Missing References (Access 2003)

Topic

New Reply

If I develop a solution in Access 2003, tell Access to convert to 2000, then load on a 2000 machine; which references are we using? More important, do you need to load vesion 11.0 DLL’s on the 2000 machine or point to version 9.0 references and hope all the VBA functions work? I’m missing something, Here. Regards Wayne

Reply | Quote

Replies

If you to develop databases to be used by Access 2000 users, it’s best to set the default database file format to Access 2000 (this is the “factory setting”, by the way). MSKB article References that you must set when you use Microsoft Office Access 2003 explains which references are set by default. The main difference between a database in Access 2002/2003 file format and one in Access 2000 format is the ADO version.

If an Access 2000 user opens a database created in Access 2003 (in Access 2000 format, of course), Access should automatically change the Access 11.0 reference to Access 9.0. In other words, they don’t need to have version 11.0 dlls.

Reply | Quote

Thanks, that confirms my sanity. The client machine, 2000, when the *.mdb was loaded, did not automatically adjust the references. In particular, I make calls to FileDialog (in MS Office 11.0) that were marked as missing. That was not an issue when the file was run on a XP-class machine with Access 2003. I scrolled down to find the 9.0 library, checked it, and tried to run the VBA… Nada! Is there a way to force the O/S to reload that library? Wayne

Reply | Quote

You have a problem here. The FileDialog object was introduced in Office XP, it is not present in Office 2000 VBA, even with the correct references. When developing for Access 2000, you should take care not to use features that were introduced in later versions. Pivot tables and pivot charts are another example.

If you want to provide an Open or Save As dialog, you can use the database attached to post 271686. It provides a class module (plus a standard module) that will work without having to set any reference, so it is independent of the Access (or Windows) version. The form in the database demonstrates its use.

Reply | Quote

You have a problem here. The FileDialog object was introduced in Office XP, it is not present in Office 2000 VBA, even with the correct references. When developing for Access 2000, you should take care not to use features that were introduced in later versions. Pivot tables and pivot charts are another example.

If you want to provide an Open or Save As dialog, you can use the database attached to post 271686. It provides a class module (plus a standard module) that will work without having to set any reference, so it is independent of the Access (or Windows) version. The form in the database demonstrates its use.

Reply | Quote

Thanks, that confirms my sanity. The client machine, 2000, when the *.mdb was loaded, did not automatically adjust the references. In particular, I make calls to FileDialog (in MS Office 11.0) that were marked as missing. That was not an issue when the file was run on a XP-class machine with Access 2003. I scrolled down to find the 9.0 library, checked it, and tried to run the VBA… Nada! Is there a way to force the O/S to reload that library? Wayne

Reply | Quote

If you to develop databases to be used by Access 2000 users, it’s best to set the default database file format to Access 2000 (this is the “factory setting”, by the way). MSKB article References that you must set when you use Microsoft Office Access 2003 explains which references are set by default. The main difference between a database in Access 2002/2003 file format and one in Access 2000 format is the ADO version.

If an Access 2000 user opens a database created in Access 2003 (in Access 2000 format, of course), Access should automatically change the Access 11.0 reference to Access 9.0. In other words, they don’t need to have version 11.0 dlls.

Reply | Quote