Microsoft Office Online
Sign in to My Office Online (What's this?) | Sign in

 
 
Microsoft Office Access
Search
Search
 
Check for updates: (c) Microsoft
Office downloads
 
 
 
Warning: You are viewing this page with an unsupported Web browser. This Web site works best with Microsoft Internet Explorer 6.0 or later, Firefox 1.5, or Netscape Navigator 8.0 or later. Learn more about supported browsers.

Email this linkEmail this link Printer-Friendly VersionPrinter-Friendly Version Bookmark and ShareShare
Synchronize and resolve conflicts in a replica set (MDB)
 

Note  The information in this topic applies only to a Microsoft Access database (.mdb).

Synchronization is the process of updating two members of a replica set (replica set: The Design Master and all replicas that share the same database design and unique replica set identifier.) by exchanging all updated records and objects in each member. Two replica set members are synchronized when the changes in each have been applied to the other. Conflicts can occur if data has changed in the same field of two replica set members that have been synchronized (synchronization: The process of updating two members of a replica set by exchanging all updated records and objects in each member. Two replica set members are synchronized when the changes in each have been applied to the other.).

ShowSynchronize with another replica set member in a database

  1. Open the replica set member you want to synchronize.
  2. On the Tools menu, point to Replication, and then click Synchronize Now. (If a Synchronizer on the Internet manages any replica set member, you will see that the managed replica (replica: A copy of a database that is a member of a replica set and can be synchronized with other replicas in the set. Changes to the data in a replicated table in one replica are sent and applied to the other replicas.) appears in the Directly with Replica drop-down list box as http://ServerName, where ServerName is the name of the Internet Server.
  3. Enter the path and file name of the replica set member you want to synchronize with the current database.
  4. If your database is the Design Master (Design Master: The only member of the replica set in which you can make changes to the database structure that can be propagated to other replicas.) and you want to make the other replica the Design Master, select the Make 'Filename' the Design Master check box. (This option is unavailable if either of the replicas to be synchronized is a partial replica (partial replica: A database that contains only a subset of the records in a full replica. With a partial replica, you can set filters and identify relationships that define which subset of the records in the full replica should be present in the database.).)
  5. Click OK.
  6. When asked whether you want to close and reopen the database, click Yes. (If you click No, you might not see all of the changes.)

ShowSynchronize a replica by using Briefcase

  1. Double-click the My Briefcase icon, and then click the database file.
  2. On the Briefcase menu, click Update Selection.
  3. Click Update to have Briefcase exchange the updates.

Note  Briefcase does not support local (local replica: A replica that exchanges data with its hub or a global replica but not with other replicas in the replica set.) or anonymous replicas (anonymous replica: In an Access database, a special type of replica in which you don't keep track of individual users. The anonymous replica is particularly useful in an Internet situation where you expect many users to download replicas.).

ShowResolve synchronization conflicts between replica set members

  1. Start the Microsoft Replication Conflict Viewer by using one of the following steps:

    Open the database that you want to check for conflicts. If there are conflicts, you are asked whether you want to resolve them. Click Yes to proceed.

    On the Tools menu, point to Replication, and then click Resolve Conflicts.

  2. In the Conflict Viewer, select a table that has conflicts from the list, and click View.
  3. For each conflict shown in the Conflict Viewer, choose one of the following options.

    To keep the data in Replica 1, click Keep existing data.

    To modify the data in Replica 1 and copy it to Replica 2 on the next synchronization, click Keep revised data.

    To keep the data in Replica 2 and overwrite the data in Replica 1 on the next synchronization, click Overwrite with conflicting data.

    To modify the data in Replica 2 and overwrite the data in Replica 1 on the next synchronization, click Overwrite with revised data.

  4. Click Resolve.
  5. Repeat steps 3 and 4 as many times as necessary to resolve each conflict in the table.

Note  The record of conflicts can be lost if you delete or move a replica (replica: A copy of a database that is a member of a replica set and can be synchronized with other replicas in the set. Changes to the data in a replicated table in one replica are sent and applied to the other replicas.). Before deleting or moving a replica, check it for conflicts.

ShowUse a different program for resolving synchronization conflicts

  1. Open the Design Master (Design Master: The only member of the replica set in which you can make changes to the database structure that can be propagated to other replicas.) for the replica set (replica set: The Design Master and all replicas that share the same database design and unique replica set identifier.).
  2. On the File menu, click Database Properties.
  3. Click the Custom tab.
  4. In the Name box, type ReplicationConflictFunction.
  5. In the Type box, click Text.
  6. In the Value box, type the name of the custom function followed by ( ). For example, if the name of the custom function is MyResolver, type MyResolver( ).
advertisement