visibility that are available in Microsoft Access:
global,
local, and
anonymous. 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 in the
replica set, and how it handles conflicts during
synchronization. The visibility also determines which replicas that replica can synchronize with.
Recommended replica use
Global |
Use to serve as a hub in a replica set. |
Local |
Use to control topology. |
Anonymous |
Use to control topology/Internet. |
Recommended for a disconnected environment on the Internet
Global |
Yes |
Local |
Yes |
Anonymous |
Yes. Anonymous replicas are recommended for Internet applications if you need a large number of replicas. |
Recommended for custom applications on the Internet
Global |
Yes |
Local |
Yes |
Anonymous |
Yes. Use the Internet as a distribution mechanism for a large number of replicas. |
Use for replica creation
Global |
Yes. Create a global, local, or anonymous replica. |
Local |
Yes. Create new local replicas. |
Anonymous |
Yes. Create new anonymous replicas. |
Use as a Design Master
Global |
Yes. When a database is replicated, the first replica that is created (the Design Master) is a global replica. |
Local |
No |
Anonymous |
No |
Database replica visibility in Access 95 and 97
Global |
Default. |
Local |
Not applicable. Don't exist in these versions. |
Anonymous |
Not applicable. Don't exist in these versions. |
Where conflict resolution is handled
Global |
Conflict resolution can be managed at any global replica. |
Local |
All conflicts are recorded and resolved at the hub (global) replica. |
Anonymous |
All conflicts are recorded and resolved at the hub (global) replica. |
Where synchronization can occur
Global |
Synchronizes with any global replica in the replica set, or any local or anonymous replica that the set created. |
Local |
Synchronizes only with its hub (global) replica. |
Anonymous |
Synchronizes only with its hub (global) replica. |
Who can schedule synchronization
Global |
Replication Manager can schedule synchronization with any global or local (child) replica. Synchronization cannot be scheduled with anonymous replicas. |
Local |
Hub replicas can schedule synchronization with a local replica. And local replicas can schedule synchronization with their hub (global) replica. |
Anonymous |
Anonymous replicas can schedule synchronization with their hub (global) replica. |
Briefcase support for synchronization
Global |
Yes |
Local |
No |
Anonymous |
No |