Show All

Hide All

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

Some of the content in this topic may not be applicable to some languages.

There are three types of 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.) visibility (visibility: A property of a replica that indicates which members of the replica set it can synchronize with and which conflict resolution rules apply. Replicas fall into three visibility types: global, local, and anonymous.) that are available in Microsoft Access: global (global replica: A replica in which changes are fully tracked and can be exchanged with any global replica in the set. A global replica can also exchange changes with any local or anonymous replicas for which it becomes the hub.), local (local replica: A replica that exchanges data with its hub or a global replica but not with other replicas in the replica set.), and anonymous (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.). A replica's visibility type determines several issues for the replica. For instance, a replica's visibility determines what type of replicas it can create from itself, whether it can act as 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.) in the replica set (replica set: The Design Master and all replicas that share the same database design and unique replica set identifier.), and how it handles conflicts during synchronization (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.). The visibility also determines which replicas that replica can synchronize with.

Recommended replica use

Recommended for a disconnected environment on the Internet

Recommended for custom applications on the Internet

Use for replica creation

Use as a Design Master

Database replica visibility in Access 95 and 97

Where conflict resolution is handled

Where synchronization can occur

Who can schedule synchronization

Briefcase support for synchronization