ACC2000: Error Message: There Were Compilation Errors During the Conversion or Enabling Of This Database...

ID: Q224340

The information in this article applies to:
  • Microsoft Access 2000
Moderate: Requires basic macro, coding, and interoperability skills.

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


ERROR MESSAGE

When you convert a database from an earlier version of Microsoft Access, 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 Access will need to recompile the database for each session.

For information on improving performance, click Help.
In rare instances, the conversion utility may fail to convert some Access Basic code to Visual Basic for Applications code. For example, it may fail to modify a DoCmd statement 

DoCmd OpenForm "MyForm"
into a method of the DoCmd object: 

DoCmd.OpenForm "MyForm"
NOTE: Microsoft Office 2000 has built-in functionality that allows you to get more information about difficult-to-troubleshoot alerts or error messages. If you want to enable this functionality for this and other error messages in Microsoft Office 2000, please download the Microsoft Office 2000 Customizable Alerts file from the Microsoft Office Update Web site at the following address:
http://officeupdate.microsoft.com/2000/downloadDetails/alerts.htm
NOTE: If you reached this article by clicking the Web Info button in an error message, you already have Customizable Alerts enabled.


CAUSE

You may receive this error for one of the following reasons:


WHAT TO TRY

Failure in conversion

To see exactly where the error(s) occur, compile all modules in the converted database.

NOTE: For compilation without errors, you may need to manually change some syntax in the database after conversion.

To compile all modules in a converted database, follow these steps:
  1. Open the converted database in the new version of Microsoft Access.


  2. Open a module in Design view.


  3. On the Debug menu, click Compile <Database Name>.


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

Back to Top

Incompatibilities with certain objects

If the conversion process seems to stop, takes a long time to complete, or displays an error that prevents the new database from being created, you can create a new database in Microsoft Access 2000 and 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 have an incompatibility with Microsoft Access 2000. If an object fails to import, then 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 and then copying it from that file later and pasting 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:
  1. Create a new Access database.


  2. On the File menu, point to Get External Data, and then click Import.


  3. In the Import dialog box, make sure to select Microsoft Access in the Files Of Type box.


  4. 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 database's icon.


  5. Click one or more objects to import. For example, you may want to import the objects in groups of 20.


  6. Click OK to import the selected objects.


  7. Repeat steps 2-6 until you have imported all the objects into the new database.


Back to Top

Errors in code in the earlier version

To help reduce errors during the conversion process, re-compile all modules and correct any errors in the database in the earlier version of Microsoft Access before converting it. This eliminates any pre-existing compile errors that would cause an error message when you convert the database to the new version.

Back to Top

Additional query words: OFF2000

Keywords : kberrmsg kbdta
Version : WINDOWS:2000
Platform : WINDOWS
Issue type : kbprb


Last Reviewed: September 15, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.