ACC95: Name Conflict Causes "Synchronization Failed" ErrorLast reviewed: August 11, 1997Article ID: Q172541 |
The information in this article applies to:
SYMPTOMSModerate: Requires basic macro, coding, and interoperability skills. When you synchronize a replica set, you may receive the following error message:
Synchronization between replica 'C:\<Path>\<ReplicaName>.mdb' and 'C:\<Path>\<OtherReplicaName>.mdb' failed. The synchronization failed because a design change could not be applied to one of the replicas. CAUSEA local object in the replica has the same name as a replicable object in the Design Master. To prevent loss of data during synchronization, Microsoft Access version 7.0 generates a design error rather than overwriting the local object with the replicable object that has the same name.
RESOLUTIONRename the local object in the replica so that the name conflict no longer occurs, and then synchronize again.
STATUSThis behavior is by design. In Microsoft Access 97, when you synchronize a replica set, and a local object in the replica has the same name as a replicable object in the Design Master, the local object is renamed <ObjectName>_Local so that it is not overwritten by the replicable object in the Design Master.
MORE INFORMATION
Steps to Reproduce Behavior
REFERENCESFor more information about design changes in replicas, search the Microsoft Access 7.0 Help Index for "replicas, changing design of," and then select the topic "Suggestions when changing the design of a replicated database."
|
Additional query words: replication
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |