MS Replication w/Access 97 with no access to server processes

[andersonm82]

Rightyho, I am in need to set up an indirectly (offline laptop-usable) synchronising database system without access to run server side processes. It looks to already work, but for testing purposes only on 3 laptops at the present time (ultimate goal - 7 to 20). In the following way;

1. Design Master resides on a network folder
2. A replica of design master (affectionately called 'replica master') resides on a network folder. Replicas are created off this.
3. Local replica resides on the windows desktop of my laptop
4. The three above are managed by a synchroniser running on my laptop.
5. Other people also have synchronisers running - managing the Replica Master, and a local copy on their desktop.
6. Dropboxes are in folders on the network drive.

This should, in theory, work perfectly.

However, there are a couple of potential problems:

1. Is there a better way of achieving the above? For example, if I set 'other people' synchronisers to manage their local replica only, will it still update the replica master? Can I set my synchroniser to stop managing the Design Master, and start it again after any changes?

2. Can use of the 'Compact Database' function cause any loss of data when using replication?

3. At one point synchronisation looked very much like it got stuck in a loop, and the log file was filled up with entries like:


Time = 2007-01-22 04:00:40 PM
Log Type = Cancel exchange
Replica = \\afsukhofs02\[folder names here]\Replica master.mdb
Exchange ID = {661D4E31-ECD1-4250-8431-285F7F3A6FFC}
Reason = Synchronizer send failure

Time = 2007-01-22 04:00:41 PM
Log Type = This other synchronizer is also managing this replica
Replica = \\afsukhofs02\[folder names here]\Replica master.mdb
SynchronizerUK20302

I assume this is because every synchroniser is set up to manage the same file, but I hoped this would not be a problem. Is question 1 the answer to this problem?

4. The log file appears to become fairly large - is there a way to reduce the information stored in it? Is the only other alternative to stick a batch file shortcut in the startup folder to delete it?

[nico5038]

I once started with replication, but wasn't really impressed. After reading the trouble it can cause (too old replica's can't be synchronized anymore, etc.) I reverted to coding my own im-/export function.
Probably most of your questions will be answered by the document you can download at:
http://support.microsoft.com/kb/q282977/

In Access 2007 replication is no longer supported and you'll have to use a Sharepoint server or the new email send/receive mechanism to get this functionality.

Nic;o)