Handling Unrecognized Database Format Error With Data Control Or Data Form Wizard

By Author: Mark Russell
Total Articles: 2
Comment this article

When it comes to maintain and store data, there is nothing as better as MS Access. This data managing application has gradually grabbed the position in every sector of business, big and small. However, at times MS Access or MDB files behave strange, restricting users to access the data and perform other operations. Slow response of MS Access database file and unexpected shutdown of MS Access application leads to stressful situations. If you are using MS Office Access 2000 database version on Windows system then there are chances that you come across slow response, complete halt of Access application.

Consider a situation when you attempt to connect to a Microsoft Access 2000 database by using either the standard Data control or the Data Form Wizard. The moment you do this you get to see the following error message where '...\databasename.mdb' is the absolute filename of the Access 2000 database:

“Unrecognized database format '...\databasename.mdb'"

Such error messages cause a condition where you find no way out to deal with this trouble. However, there is surely a way out to handle this error message. ...
... Before you head to find solution, knowing the actual cause is necessary.

Cause behind this error message

For the above-mentioned behavior, following are the possible cause:

1) The standard Data control uses Data Access Object (DAO) 3.51 to connect to Access databases by using the Jet 3.51 engine.

2) The Data Form Wizard uses the Jet 3.51 OLE DB Provider to connect to Access databases by using the Jet 3.51 engine.

3) The Jet 3.51 engine can connect to Access database versions prior to Access 2000, but cannot connect to Access 2000 databases.

Solution to this trouble

The above-mentioned problems are not noticeable with the Data control and Data Form Wizard that ship with Microsoft Visual Studio 6.0 Service Pack 4 and later. In case, you are using the Data Control, an additional step must be taken to change 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. The workarounds for the Data Form Wizard problem were:

5) Open the Access database through an ODBC DSN that uses the Access ODBC driver version 4.0.

6) Build the form manually using Jet 4.0 to connect to the database.

At times, these workarounds do not work if the cause of error is complex or is unknown to users. In both the conditions, it is necessary that a feasible solution be explored. The solution to this problem exists in the form of Kernel for Access Repair software. This repair mdb file tool rebuilds and repairs corrupt access database files, which get corrupted due to an unexpected software crash, virus corruption or database synchronization failure. Repair MDB software comes with two recovery modes, which can be used according to the intensity of the corruption in the .mdb file. This professionally created software provides accurate and complete recovery of the data from inaccessible MDB file.

for about any information

visit for site

http://www.mdbrepairtool.net