Resolving Replication Conflicts
When the Jet Engine tries to synchronize two databases, it might find that the same row has been changed in both databases, resulting in a conflict that must be handled. The rule is that the database in which the row has changed most often wins. If both rows have changed the same number of times, Access chooses the winner randomly. This might sound frightening, but it isn't as bad is it seems because you can let the user know which changes were rejected.
You must know whether two members of the replica set contain conflicting information. Two users out in the field might have entered different information about a sale or a customer, so it's important that the program identify these inconsistencies and have a method ...
Get Alison Balter's Mastering Access 2002 Enterprise Development now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
