Symptoms

After removing a database from replication, SPEED Ferret may continue to treat the database objects as read-only.

Cause

Every Access 97 database contains two properties that can be used to determine its replication status. They are:

• CurrentDB.DesignMasterID
• CurrentDB.ReplicationID

In a new database, these properties are both empty. When you place a database under replication, these properties will contain GUID's (Globally Unique ID's). In the design master, the two GUID's will be identical. In a replica the GUID's will be different.

SPEED Ferret for Access 97 determines the replication status of the current database by comparing the DesignMasterID property with the ReplicaID property. If the two properties are not equal, SPEED Ferret assumes that the database is a replica, and treats all of the database objects as read-only.

If you are working with a database that was once a replica, but was removed from replication, it is possible that the ReplicaID property was cleared and is now a zero-length string. But the DesignMasterID may not have been cleared. In this case SPEED Ferret for Access 97 will incorrectly conclude that the database is still a replica, because the DesignMasterID and ReplicaID are not identical.

Workaround

It is not possible to assign a zero-length string to the DesignMasterID property, and the ReplicaID property is read-only. So there appears to be no way to completely restore the database to its pre-replication state.

The only workaround for this problem is to create a new database and import all of the objects from the original database.