What's new in replication?

Microsoft Replication Manager

What's new in replication?

Replication commands on the Microsoft Access Tools menu in a Microsoft Access database (.mdb) and in a Microsoft Access project (.adp) allow you to create replicas and synchronize them on demand as you work in Microsoft Access.

  • Replication in an Access project   Replicate data in an Access project by creating publications and subscriptions.

  • Jet and Replication Objects (JRO)   JRO includes methods and properties developers can use to programmatically replicate and synchronize databases and Access projects.

  • Web server replication   Work on files even when you are no longer connected to a Web server.

  • Replica priority   A replica in a replica set is assigned a priority when it is created. The highest priority replica wins in the case of a synchronization conflict.

  • Prevent deletes option   Prevent users from deleting records in a replica.

  • Local and anonymous replicas   Create local replicas and anonymous replicas. Local and anonymous replicas can synchronize only with their parent, global replica. Anonymous replicas are recommended for Internet applications if you need a large number of replicas.

  • Conflict Viewer   The Conflict Viewer is the default tool in Access to reconcile and resolve synchronization conflicts.

  • Row Level Tracking property   When this table property is set to True, it indicates that conflicts are tracked based at the row-level of a table. Conflicts are tracked at the column-level by default.

  • ConflictFunction property   This property is used to replace the Microsoft Access Conflict Viewer with a customized procedure that assists users in resolving synchronization conflicts.

  • Retention Period   Controls the number of days nonsynchronized records are retained in the system tables.

  • Synchronization conflicts   A single mechanism is now used to record and resolve conflicts and errors, making it easier to resolve conflicts. Whenever a conflict occurs, a winning change is selected and applied in all replicas and the losing change is recorded as a conflict at all replicas.

  • Column-level conflict resolution   Conflicts are determined at the column level. Changes to the same record in two different replicas cause a synchronization conflict only if the same column or field is changed.