DAO, Database Replication, and Conflicts

Hello all,

I have a question regarding using DAO for database replication. How are conflicts resolved??? For example, if the same record in both the Design Master and the Replica are changed how does Microsoft Jet handle this when the databases are synchronized???

Thanks in advance for you help.

Regards, Anthony

[lychew]

this is what i found:

If two users at two separate replicas each make a change to the same record in the database, the changes made by one user will fail to be applied to the other replica. Consequently, the user with the failed change must resolve the conflicts.

Conflicts occur at the record level, not between fields. For example, if one user changes the Address field and another updates the Phone field in the same record, then one change is rejected. Because conflicts occur at the record level, the rejection occurs even though the successful change and the rejected change are unlikely to result in a true conflict of information.

The synchronization mechanism handles the record conflicts by creating conflict tables, which contain the information that would have been placed in the table, if the change had been successful. You can examine these conflict tables and work through them row by row, fixing whatever is appropriate.

All conflict tables are named table_conflict, where table is the original name of the table, truncated to the maximum table name length.