ACC2000: Error Message: "Visual Basic for Applications Project in This Database Is Corrupt"

View products that this article applies to.

This article was previously published under Q248960

Moderate: Requires basic macro, coding, and interoperability skills.

This article applies only to a Microsoft Access database (.mdb).

Expand all | Collapse all

SYMPTOMS

When you try to open the Visual Basic Editor in a Microsoft Access database (by pressing ALT+F11), you may receive one or more of the following error messages:

The Visual Basic for Applications project in this database is corrupt.

-or-

The module name 'module name' is misspelled or refers to a module that doesn't exist.

If the invalid module name is in a macro, an Action Failed dialog box will display the macro name and the macro's arguments after you click OK. Open the Macro window, and type the correct module name.

If you then try to close the database, Access may stop responding, or you may see one of the following error messages.

If you are running Microsoft Windows 95 or Microsoft Windows 98:

This program has performed an illegal operation and will be shut down.

If the problem persists, contact the program vendor.

When you click Details (on Microsoft Windows Millennium Edition, press ALT+D), you receive the following message:

MSACCESS caused an invalid page fault in MSACCESS.EXE at 0137:3002d909.

NOTE: The actual memory address may vary.

If you are running Microsoft Windows NT:

An application error has occurred
and an application log is being generated.

MSACCESS.exe
Exception access violation(ox0000005),Address; 0x3002d681

You also see the following error message when you try to compact the database:

The Visual Basic for Applications project in this database is corrupt.

Back to the top

CAUSE

The Visual Basic for Applications project is corrupted.

Back to the top

RESOLUTION

Forms, reports, and modules use Visual Basic for Applications. If the Visual Basic for Applications project is corrupted, forms, reports, and modules are affected by this corruption and cannot be restored.

To save your tables, queries, and macros, follow these steps:

Create a new blank database.
Open the problem database, and then click Tables under Objects.
Right-click the first table, and then click Export on the shortcut menu.
In the Export to dialog box, browse to the database that you created in step 1.
Click that database, and then click OK.
Repeat steps 4 through 6 for each table, query, and macro.

NOTE: When you try to export forms, reports, or modules, you will receive the error messages detailed at the beginning of this article.

Back to the top