My code can't compile.

My code can't compile.

When you convert a Microsoft Access version 2.0 database to Microsoft Access 2000, the conversion utility converts Access Basic code to Visual Basic for Applications (VBA) code. If any code doesn't successfully compile, you may receive an error message after you convert to Microsoft Access 2000.

In the converted Access database, open a module in Design view and click Compile All Modules on the Debug menu. As Microsoft Access compiles, it stops at any line of code that contains an error. You can then modify the syntax to resolve the compile error.

In rare instances, the conversion utility may fail to convert some syntax. For example, it may fail to modify a DoCmd statement into a DoCmd method. You may also receive compile error messages if your Microsoft Access version 2.0 database contains syntax errors. For this reason, it is a good idea to compile all of your previous-version database modules before you convert them to Microsoft Access 2000.

Microsoft Access 2000 does not support the DAO 2.5/3.x compatibility library. If you attempt to convert a database in which the code contains older versions of DAO objects, methods, and properties that depend on the DAO 2.5/3.x compatibility library, you receive a message that there were compilation errors during the conversion of the database. Before you convert the database, update the code so that it does not depend on the DAO 2.5/3.x compatibility library. If you still receive a message that there were compilation errors during conversion, open the converted database in Microsoft Access 2000, remove the reference to the missing DAO 2.5/3.x compatibility library, and then set a reference to the Microsoft DAO 3.6 Object Library. For information about changes to methods, actions, properties, syntax, and other language elements, and information about code compatibility and conversion issues, click .