You receive a "There were compilation errors during the conversion or enabling of this database" error message when you convert a database from an earlier version of Access to Access 2002 or Access 2003 (324350)

ERROR MESSAGE

When you convert a database from an earlier version of Microsoft Access to Microsoft Access 2002 or Microsoft Office Access 2003, you may receive the following error message:

There were compilation errors during the conversion or enabling of this database. The database has not been saved in a compiled state. The performance of this database will be impaired because Microsoft Access will need to recompile the database for each session.

For information on improving performance, click Help.

In rare instances, the conversion utility may not convert some Access Basic code to Visual Basic for Applications code. For example, it may not change a DoCmd statement

DoCmd OpenForm "MyForm"

into a method of the DoCmd object:

DoCmd.OpenForm "MyForm"

Note Microsoft Office XP has built-in functionality that allows you to get more information about difficult-to-troubleshoot alerts or error messages. If you want to turn on this functionality for this and other error messages in Microsoft Office XP, download the "Office XP add-in: extended alerts button" file from the following Microsoft Office Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=8FBEE1D3-C5BB-4A36-A2F7-DC63DE2A818C&displaylang=en

NOTE: If you reached this article by clicking Web Info in an error message, you already have Customizable Alerts turned on.

THINGS TO TRY

Conversion Errors

To see where the error or errors occur, compile all modules in the converted database.

Note For compilations that do not have any errors, you may still have to manually change some syntax in the database after conversion.

To compile all modules in a converted database, follow these steps:

Open the converted database in the new version of Microsoft Access.
Open a module in Design view.
On the Debug menu, click Compile <Database Name>.

As Microsoft Access compiles your code, it stops at any line that contains an error. You can then modify the syntax to resolve the compilation error.

Incompatibilities with Certain Objects

If the conversion process seems to stop, takes a long time to finish, or displays an error that prevents the new database from being created, you can create a new database in Microsoft Access 2002. You can then import objects (individually or grouped) from the database in the earlier version.

Importing objects into a new database has two benefits:

You can speed the conversion process by importing groups of objects. If you have a large database, the conversion process may be slow or may appear to cause your computer to stop responding. Importing groups of objects requires less memory and, in some cases, may be faster.
You can determine which objects are incompatible with Microsoft Access 2002. If an object cannot be imported, you know to examine it more closely for a potential incompatibility. If an object is imported successfully, it is automatically converted to the new version.

NOTE: In rare instances, corruption in an object may cause incompatibility with the later version of Access. If you suspect corruption, do not import that object. Instead, re-create it in the later version of Access. If the object is a Visual Basic for Applications procedure, try copying the text to a Notepad file. Then, copy it from that file later and paste it into a new module in the later version of Access.

To use the Import command instead of the Convert Database command, follow these steps:

Create a new Access database.
On the File menu, point to Get External Data, and then click Import.
In the Import dialog box, click Microsoft Access in the Files of type box.
Click the arrow to the right of the Look In box, select the drive and folder where the Microsoft Access database (.mdb) that you want to import is located, and then double-click the icon of the database.
Click one or more objects to import. For example, you may want to import the objects in groups of 20.
Click OK to import the selected objects.
Repeat steps 2 through 6 until you have imported all the objects into the new database.

Errors in Code in the Earlier Version

To reduce the number of errors that may occur during the conversion process, recompile all modules in the earlier version database. Then correct any errors before you convert the database.