Replication Question

[Sandy H]

Does anyone know how replicated databases work when it comes to changes to
data (as opposed to new records being added).

For example, a membership database has a master db in Australia and a couple
of replicas in the US and the UK. All the records are synchronised. The UK
replica database records a change of address for a member and then some time
later, the replica is synchronised with the Master in Australia.

How does the Master database know which is current member's address? (The
master has the old address and the replica has the new address.

I can't get my mind around this and would appreciate any information.

Thanks in advance

Sandy

 

[Mark]

This question would be best answered if it were posted to
microsoft.public.access.replication.

But I believe the answer is something along the lines of: Access keeps track
of when the changes to records occur in replicas. When it synchronizes, it
checks each record against the records in the other database and if anything
is different, it checks for the most current "updated timestamp" and the
most recent changes are applied. If you have Record-level tracking turned
on, if two users update different fields in the same record, a conflict
comes up which requires you to decide which record gets updated and which
gets dropped. If Record-level tracking is off, then you only get conflicts
if two users change the same field in the same record.