When you try to view the code for a module, try to compile a database, try to create an MDE file, or try to execute code in a Microsoft Access 2000 database, you may receive one of the following error messages:

You may receive one of these error messages when both Microsoft Access 2000 and version 6.3.91.8 of the Vbe6.dll file are installed on the computer, and either of the following conditions is true:

• You imported forms or reports that contain code modules or standalone modules into a new Microsoft Access 2000 database by using Microsoft Access 2000.
• You copied and pasted forms or reports that contain code modules or standalone modules into the Microsoft Access 2000 database by using Microsoft Access 2000.

Then, you close and reopen the database and try to view, execute, or compile the code.

If you have a computer without the version of Vbe6.dll that is mentioned in the "Cause" section, you may be able to repair the problem with the following steps:

1. Open a form or a report in Design view.
2. Save the code behind the form or the report as a text file.
3. Set the form or the HasModule property of the report to No, and then save the object.
4. Repeat step 1 through step 3 for each form and report in the database.
5. Save each module as a text file.
6. Create a new blank database.
7. On the File menu, point to Get External Data, and then click Import. Import all tables, queries, forms, reports, data access pages, and macros to the new database.
8. Restore the code behind each form and each report from the text files that you created in step 1 through step 4.
9. Import each text file that you saved in step 5 as a new module.

If you do not have a computer without the version of Vbe6.dll mentioned in the "Cause" section, you must revert to a known good backup copy of the database. To prevent this problem from happening again, use one of the following methods, depending on which version of Access you are using.

Using Access 2000

Method 1

To prevent this problem from happening again, obtain the latest service pack for Microsoft Office 2000. You must install this service pack on all computers that run Office 2000.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base: IMPORTANT: Before you install Microsoft Office 2000 Service Pack 3 (SP-3), you must have Microsoft Office 2000 Service Release 1/1a (SR-1/SR-1a) installed first.

For additional information about how to obtain Office 2000 Service Release 1/1a (SR-1/SR-1a), click the following article number to view the article in the Microsoft Knowledge Base: Method 2

1. When you import to a new database, create a new database and import the objects into the new database. Or, when you copy objects in the current database, copy and paste the objects into the current database.
2. Before closing the database, open the Visual Basic Editor by pressing ALT+F11.
3. On the Debug menu, click Compile <database name>.
4. After you compile the database, close and save the database. Note that when you reopen the database and view the code, the error message that is mentioned in the "Symptoms" section of this article does not occur.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Some of the programs that include Vbe6.dll version 6.3.91.8 are Microsoft Office XP, its component applications, and Microsoft Visio 2002. The version number of Vbe6.dll may also appear as 6.03.9180, depending on the version of Windows that you are using.

Steps to Reproduce the Behavior

1. On a computer that has both Microsoft Access 2000 and version 6.3.91.8 of the Vbe6.dll installed, open Microsoft Access 2000.
2. In Microsoft Access 2000, create a new blank database and name it ImportTest.mdb.
3. On the File menu, point to Get External Data, and then click Import.
4. Browse to the sample database Northwind.mdb for Microsoft Access 2000.
5. In the Import Objects dialog box, click the Modules tab.
6. Click the Startup module, and then click OK.
7. After successfully importing the Startup module, close the ImportTest database.
8. In Microsoft Access 2000, open the ImportTest database.
9. Open the Startup module in Design view. Note that you receive one of the error messages that is mentioned in the "Symptoms" section of this article, and you are then unable to view the code for the Startup module.