Replication Properties

Microsoft Jet adds new properties to your database when it becomes replicable: ReplicableBool, Replicable, ReplicaID, and DesignMasterID. The ReplicableBool property replaces the Replicable property used in prior versions of Microsoft Jet. The Replicable property is still available but is used only to maintain backward compatibility and should not be used. The ReplicableBool property is set to True, indicating the database is now replicable. After the property is set to True, however, it cannot be changed. Setting the property to False returns an error. The ReplicaID property is a 16-byte value that uniquely identifies the Design Master or replica.

The DesignMasterID property can be used to make a replica the new Design Master for the replica set. This property is set for the Design Master when the database is initially made replicable. Under extreme circumstances — for example, the loss of the original Design Master — you can set the property for the current replica. However, setting this property for a replica, when there is already another Design Master, might partition your replica set into two irreconcilable sets and prevent any further synchronization of data. If you determine that it is necessary to set this property for a replica, first synchronize the replica with all other replicas in the set.

Caution Never create a second Design Master in a replica set. The existence of a second Design Master can result in the loss of data.

There are two new properties that you can append and set on the individual tables, queries, forms, reports, macros, and modules in your database: KeepLocal and ReplicableBool. To prevent an object from being copied to other replicas in a replica set, you can set the KeepLocal property of the object to “T” prior to converting the database into a replicable form. After the database is converted, you can set the ReplicableBool property to True to make a local object replicable. For more information about these two properties, see the “Replicating Your Database” section earlier in this chapter.

Microsoft Jet also adds the ColGeneration property to Memo (Long Text) and OLE Object (Long Binary) fields to identify the name of the field used to track generations for these fields.