Hi,
I am trying to find an easier way to rebuild my system of 4 replica's where I have 5 tables that can't be syncronised because the data changes dramatically and would cause many conflicts.
Access 2007 but using 2003 data to keep replication & MDE (runtime ability) as some computers don't have full office copies.
If I make any small design changes or rebuild to single master because system might get unstable (Rarely, though) I have to:-
1) Import tables into existing design master mdb backup. Delete all other replica's.
2) Make as MDE
3) Create Replica's (over the wireless LAN)
4) Edit the properties of the 5 tables to not replicate.
5) Sync them all, then from the main computer open the other replica's via the LAN, import the unreplicated tables and repeat.
This is painfully slow as running access effectively from the networked computer is asking a lot even though computers are fast & network running pretty fast.
Is there an easier way, I am trying to avoid major design changes as I programmed the system many years ago and whilst done a few tweeks not really that sharp on the programming nowadays. Reading other threads people seem to hate replication but I don't think I have the skills to make major changes any more. This system has worked for 10'ish years, never, ever had a full system failure. Over reliable wireless LAN, again never crashed due to a WiFi failure.
Rebuilt a few times a year as perhaps not running correctly but generally because I change something.
It there a function that could automatically check & change the property of these tables when each replica is started.
I am guessing maybe front end back end stuff, but I am not familiar with this and suspect still issues.
I don't mind building back from the mdb but the importing tables etc. especially if I was away on holiday and system died, I could never talk anyone through the whole procedure.
Any ideas would be appreciated, but keeping as simple as possible.
Many thanks I/A.
I am trying to find an easier way to rebuild my system of 4 replica's where I have 5 tables that can't be syncronised because the data changes dramatically and would cause many conflicts.
Access 2007 but using 2003 data to keep replication & MDE (runtime ability) as some computers don't have full office copies.
If I make any small design changes or rebuild to single master because system might get unstable (Rarely, though) I have to:-
1) Import tables into existing design master mdb backup. Delete all other replica's.
2) Make as MDE
3) Create Replica's (over the wireless LAN)
4) Edit the properties of the 5 tables to not replicate.
5) Sync them all, then from the main computer open the other replica's via the LAN, import the unreplicated tables and repeat.
This is painfully slow as running access effectively from the networked computer is asking a lot even though computers are fast & network running pretty fast.
Is there an easier way, I am trying to avoid major design changes as I programmed the system many years ago and whilst done a few tweeks not really that sharp on the programming nowadays. Reading other threads people seem to hate replication but I don't think I have the skills to make major changes any more. This system has worked for 10'ish years, never, ever had a full system failure. Over reliable wireless LAN, again never crashed due to a WiFi failure.
Rebuilt a few times a year as perhaps not running correctly but generally because I change something.
It there a function that could automatically check & change the property of these tables when each replica is started.
I am guessing maybe front end back end stuff, but I am not familiar with this and suspect still issues.
I don't mind building back from the mdb but the importing tables etc. especially if I was away on holiday and system died, I could never talk anyone through the whole procedure.
Any ideas would be appreciated, but keeping as simple as possible.
Many thanks I/A.