This article was previously published under Q257780
When you attempt to connect to a Microsoft Access 2000 database by using either the standard Data control or the Data Form Wizard, you see the following error message where '...\databasename.mdb' is the absolute filename of the Access 2000 database:
Unrecognized database format '...\databasename.mdb'"
The standard Data control uses Data Access Object (DAO) 3.51 to connect to Access databases by using the Jet 3.51 engine.
The Data Form Wizard uses the Jet 3.51 OLE DB Provider to connect to Access databases by using the Jet 3.51 engine.
The Jet 3.51 engine can connect to Access database versions prior to Access 2000, but cannot connect to Access 2000 databases.
These problems are not seen with the Data control and Data Form Wizard that ship with Microsoft Visual Studio 6.0 Service Pack 4 and later. (If you are using the Data Control, you must take the additional step of changing its Connect property to Access 2000.)
Prior to service pack 4 for Visual Studio 6.0, the workaround for the standard Data control problem was to open a Recordset using DAO code, and then assign it to the Data control's Recordset. This workaround is described in Microsoft Knowledge Base article Q238401 in the "References" section.
Prior to service pack 4 for Visual Studio 6.0, the workarounds for the Data Form Wizard problem were:
Open the Access database through an ODBC DSN that uses the Access ODBC driver version 4.0.
Build the form manually using Jet 4.0 to connect to the database.
See these workarounds in the Microsoft Knowledge Base article Q242010 in the "References" section.
NOTE: There are known issues when connecting to Access 2000 on certain localized versions of Visual Basic 6.0 Service Pack 4. This is scheduled to be fixed in Visual Basic 6.0 Service Pack 5. However, this bug is fixed for the English version (North America) of Visual Basic 6.0 Service Pack 4.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in the latest service pack for Visual Studio 6.0.
For additional information about Visual Studio service packs, click the following article numbers to view the articles in the Microsoft Knowledge Base:
194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why
194295 HOWTO: Tell That a Visual Studio Service Pack Is Installed
To download the latest Visual Studio service pack, visit the following Microsoft Web site: