Article ID: 224340
Article Last Modified on 1/9/2007
APPLIES TO
- Microsoft Access 2000 Standard Edition
This article was previously published under Q224340
Moderate: Requires basic macro, coding, and interoperability skills.
This article applies only to a Microsoft Access database (.mdb).
For a Microsoft Access 2002 version of this article, see 324350.
THINGS 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:
- 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. At that point, you can modify the syntax to resolve the compilation error.
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:
- Create a new Access database.
- On the File menu, point to Get External Data, and then click Import.
- In the Import dialog box, make sure to select 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 database's icon.
- 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-6 until you have imported all the objects into the new database.
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.
MORE INFORMATION
For additional information about other problems you may encounter when you try to convert a database to Access 2000, click the article number below to view the article in the Microsoft Knowledge Base:
225946 ACC2000: Corrupted VBA Project Error When You Try to Convert a Database
Additional query words: OFF2000
Keywords: kberrmsg kbdownload kbprb KB224340
