Share this Page URL

Chapter 10. Multiuser Applications > Create a Transaction Log - Pg. 452

· Changes any sequentially assigned AutoNumber fields to randomly assigned Au- toNumber fields to reduce the possibility of AutoNumber conflicts When you synchronize replicas, Access compares records in each replica using the hidden s_Generation field to determine if records have been updated. During synchro- nization, only changed rows are exchanged between replicas. When conflicting edits are detected during a synchronization exchange, Access deter- mines which edited version of a record "wins" an exchange using the following rules: · If a record in one replica was changed more times than in the other replicas, it wins. · If all copies of a record were changed an equal number of times, Access randomly picks a winner. Only users with "losing" edits are notified of conflicts. Replication works best when your replicas are only loosely coupled, and it isn't critical that all changes be synchronized as soon as they are made. It is best to replicate only tables, and not forms, reports, or other Access objects. Although Access supports rep- licating other database objects, it doesn't always work well. You may find that in at- tempting to synchronize design changes, only partial changes are propagated to the replicas, creating additional headaches. In addition, Access replication is suitable only when you anticipate a small or moderate number of updates to the same records in different replicas. If you need real-time synchronization or if you anticipate a high number of updates to the records across replicas (conflicts), you may wish to consider