Unrecognized database format

p.lorens

Registered User.
Local time
Today, 23:16
Joined
Oct 4, 2005
Messages
11
Hello. Just got the following message when trying to open a database file: "Unrecognized database format '[filename]'.

Do anyone know why this occurs, and more important, do anyone know if it's possible to fix it?
 
Could be the MDB was created in a newer version of Access. Or the MDB is not really an MDB or its corrupted.
 
I've been using this mdb-file for a long time, and it's linked via DAO-code in a VB6 program. The error happened after a hang, and I had to shut down my computer. I've also had this problem before, but luckily I had a backup of the file.

But, I'm curious of what happens, and I also would very much like to find a solution to this problem. It's not version related.
 
To me, this is access' greatest flaw... It's not at all that stable when used in the wrong way.

Multi-user environments are always dangerous. When the database runs on a non-windows server, you're guaranteed to run into trouble too.

Luckaly you can (almost) always save your database from destruction. 'Repair and Compact' works like a charm. If that doesn't work, you'll be able to fine some tools to extract your data if the database appears to be a total loss.

I don't really know why this happens, but I'm running most of my databases with an Access-frontend and I store my data on a MS-SQL Server database. Quite a costly sollution, but hey, the company pays ;-) Since then, I never ever crashed again! (Oh-oh, not sure I should have said this out loud! ;-)

Seth
 
Thank you for sharing my concern.

Do you have any examples of software ment for fixing when total loss. I can't get into the DB through linking, and the file is unopenable, so although I had a backup this time, I fear this may happen again.

So, if anyone has good software or code for fixing a totally defect mdb-fil, please inform.
 
Try this.........

This little tool lets you compact and repair a lot of corrupted databases. There has only been 1 db that I have not been able to use this on.

The Jetcu4 file is for Access 2000. might work for 2003.
 

Attachments

Last edited:
Unfortunately, it didn't work on my MS Access 2003 DB.
 
I still can't fix the database file. The file downloaded from microsoft was the same file downloaded earlier from this thread. Seems like the file is unfixable.
 
Have you tried to create another DB and import the objects from the source DB?

Are you able to connect to it from your VB app?

Are you able to connect to it from other ODBC sources, say, like Excel or another Access DB?
 
I am having what seems to be the same issue described above. I have tried the Jet Compact Utility to no avail. I also attempted to import the objects into a new, blank DB and linking from Excel, but I keep getting the same error message. The other thing that I noticed is that the “damaged” database is a little less then half the size of my last backup. Any recommendations?
 

Users who are viewing this thread

Back
Top Bottom