ACC97: Removing Replicated Module Causes Automation ErrorLast reviewed: November 11, 1997Article ID: Q171207 |
The information in this article applies to:
SYMPTOMSAdvanced: Requires expert coding, interoperability, and multiuser skills. When you open a replica after synchronizing with another replica, you may receive the following error message:
Automation error CAUSEAn object in the Design Master's Visual Basic for Applications project has been made nonreplicable, and then a synchronization with the replica has been performed from within the Design Master.
RESOLUTION
Correcting the Automation Error After SynchronizationCorrecting 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:
Preventing the Automation Error from OccurringYou 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:
STATUSMicrosoft 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://www.microsoft.com/office/office97/servicerelease MORE INFORMATIONObjects 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 BehaviorCAUTION: 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.
|
Additional query words: pra
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |