ACC95: Name Conflict Causes "Synchronization Failed" Error (172541)
The information in this article applies to:
- Microsoft Access for Windows 95 7.0
This article was previously published under Q172541 Moderate: Requires basic macro, coding, and interoperability skills.
SYMPTOMS
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.
CAUSE
A 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.
RESOLUTION
Rename the local object in the replica so that the name conflict no longer
occurs, and then synchronize again.
STATUS
This 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.
REFERENCES
For 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."
Modification Type: | Major | Last Reviewed: | 11/17/2000 |
---|
Keywords: | kberrmsg kbprb KB172541 |
---|
|