Microsoft Replication Conflict Viewer displays "<No conflict tables>" even when synchronization conflicts exist among the replicas in Microsoft Access (883870)


The information in this article applies to:

  • Microsoft Office Access 2003
  • Microsoft Access 2002
  • Microsoft Access 2000

This article applies only to a Microsoft Access database (.mdb).

Advanced: Requires expert coding, interoperability, and multiuser skills.

SYMPTOMS

When you try to synchronize the members of a replica set in Microsoft Access, you may notice that synchronization conflicts may occur. You may receive the following error message:
This member of the replica set has conflicts from synchronizing changes with other members.
Do you want to resolve these conflicts now?
However, when you click Yes to resolve synchronization conflicts by using Microsoft Replication Conflict Viewer, you may notice that Replication Conflict Viewer does not display the list of tables that are involved in synchronization conflicts. The Tables with conflicts list in the Microsoft Replication Conflict Viewer dialog box displays <No conflict tables>.

Therefore, you cannot resolve synchronization conflicts in the replica of your Access database.

CAUSE

One of the replicas in your replica set that you are trying to synchronize is corrupted.

The MSysConflicts system table stores information that is related to each conflict in your replica set. Notice that the MSysConflicts system table displays the following message to explain why a synchronization conflict has occurred. The following message is displayed in the Reason column of the MSysConflicts system table:

Recovered replicable data. This row was recovered from a corrupted replicable database. Verify that the record contents are correct and then reinsert the record, or delete the conflict record.

WORKAROUND

To work around this problem, you must resolve synchronization conflicts manually. To do this, follow these steps:
  1. Start Access, and then open your replicated Access database.
  2. In the Database window, click Options on the Tools menu, and then click the View tab.
  3. In the Show section, click to select the Hidden objects check box, click Apply, and then click OK.
  4. In the Database window, click Tables in the Objects section.
  5. In the right pane, examine all the tables to verify whether there are additional tables that are named <Table Name>_Conflict.

    Note The placeholder that is named <Table Name> is a placeholder for the name of the table that is involved in the synchronization conflict.

    For example, if there is a conflict in the Customers table, an additional table that is named the Customers_Conflict table is created during the synchronization.
  6. Write down the details of all the records in the tables that are identified in step 5, and then delete the tables.

    Notice after you delete the tables with the _Conflict suffix, you do not receive the synchronization conflict error message that is mentioned in the "Symptoms" section.
  7. Resolve the conflicts manually by comparing the records in your table and the records in the conflict table that correspond to your table. Then, correct the conflicting records in your table.

REFERENCES

For additional information about database replication in Microsoft Jet 4.0, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn.microsoft.com/library/en-us/dnacc2k/html/dbrepjet.asp

Modification Type:MajorLast Reviewed:8/23/2004
Keywords:kbReplication kbDatabase kberrmsg kbtshoot kbprb KB883870 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.