ACC97: Removing Replicated Module Causes Automation Error (171207)

RESOLUTION

Correcting the Automation Error After Synchronization

Correcting the Automation error following synchronization depends on how the object was made nonreplicable in the Design Master. If the object was made nonreplicable by clearing the Replicable check box in the object's property window, the error should be corrected after you open the replica a second time following synchronization. The first time you open the replica following synchronization, Microsoft Access automatically compiles and saves the replica's Visual Basic for Applications project. Once Microsoft Access has compiled and saved the replica's Visual Basic for Applications project, you should no longer receive the error when opening the replica.

If the object was made nonreplicable by deleting it from the Design Master, you will continue to receive the Automation error each time you open the replica. In this case, you can correct the error by manually compiling and saving all modules in the replica. To manually compile and save all modules in the replica, follow these steps:

Open the replica that is producing the Automation error.
Create a new, local module.
On the Debug menu, click "Compile and Save All Modules." When prompted to save the module, save it with any name.
Delete the new module created in step 3.
Close the replica, and then reopen it. Note that the Automation error no longer occurs.

Preventing the Automation Error from Occurring

You can prevent the Automation error from occurring by performing the synchronization from within the replica. This causes Microsoft Access to automatically compile and save the replica's Visual Basic for Applications project, and therefore prevents the error from occurring. To initiate the synchronization from within the replica, follow these steps:

Open the replica.
On the Tools menu, point to Replication, and then click Synchronize Now.
Select the Design Master database, and then click OK. You will receive a message confirming the synchronization was completed successfully. Click Yes to close the message.
Close the replica, and then reopen it.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access 97. This problem no longer occurs in Microsoft Access 97 Service Release 1.

NOTE: Stand-alone Microsoft Access 97 Service Release 1 is not currently available, but you can update your copy of Microsoft Access 97 to Service Release 1 by downloading Microsoft Office Service Release 1 from Microsoft's Web site at:

http://office.microsoft.com/en-us/assistance/HA010449921033.aspx

MORE INFORMATION

Objects that make up a database's Visual Basic for Applications project include global modules as well as forms and reports whose HasModule property is set to Yes. These objects can be made nonreplicable either by clearing the Replicable check boxes or by deleting the objects from the Design Master.

Steps to Reproduce Behavior

CAUTION: Following the steps in this example will modify the sample database Northwind.mdb. You may want to back up the Northwind.mdb file and perform these steps on a copy of the database.

Open the sample database Northwind.mdb.
Create a module and type the following line in the Declarations section if it is not already there:
```
       Option Explicit
						
```

Type the following procedure:

       Function Test()
          MsgBox "This is a test."
       End Function

On the Debug menu, click "Compile and Save All Modules."
When prompted for the module name, type mdlReplicationTest, and then click OK. Close the module.
On the Tools menu, point to Replication, and then click Create Replica.
Click Yes when prompted to close the current database.
Click No when prompted to create a backup of the database.
Select a location for the new replica, and then click OK. You will receive a confirmation message indicating the database has been converted to a Design Master, and that a replica has been created. Click OK to close the message.
Open the replica created in steps 6 - 9. Note that Microsoft Access compiles and saves the replica's Visual Basic for Applications project without error.
Open the replicated version of Northwind.mdb.
Delete the "mdlReplicationTest" module created in steps 2 - 5.
On the Tools menu, point to Replication, and then click Synchronize Now.
Select the replica created in steps 6 - 9, and then click OK. You will receive a message confirming the synchronization was completed successfully. Click Yes to close the message.
Open the replica created in steps 6 - 9. Note that you receive the following error message:
Automation error