Unrecognized Database Format

[stevenz]

Recently when I try to open some of my Access databases I get the error Unrecognized database format <database path and name>
I have tried the following:
- Renaming the database
- Moving the database to another folder
- Create a blank new database and importing the table, queries, forms etc from the old database.
- Opening the database from the command line with the /compact and /decompile options
but nothing works.

Any idea how to recover the databases or what the error could be.

I am running Windows 7 Professional (64-bit) and Office Professional Plus 2013 (32-bit)

 

[dhookom]

You have tried most of what I would suggest.
Do you have recent backups?
Is your database split so at least your data might still be good?
Do any other databases open correctly?

There are some paid services that do a fairly good job of restoring files that are corrupt.

Duane
Hook'D on Access
MS Access MVP

 

[randy700]

Are you by any chance trying to open a newer version from an older version?
For example: if the DB was designed in Access2010 and you're using Access2003, it ain't gonna work!



Randy

 

[stevenz]

Hello dhookom

The database is not a split database.
I import a lot of data into the database and then have various reports that I run.
Maybe the repeated deleting of data and re-importing of data somehow corrupted the database.
Although this specific error is a new one for me.
The database is set to compact on close.

Fortunately I do have recent backups.
All my other databases currently open correctly.
I will monitor if other databases get corrupted in the future.

I just thought a recent windows or office patch might have something to do with this.

Thanx anyway

 

[stevenz]

Hello randy700

No, the database is a Access 2013 database.
I am not opening an old version of Access.

Thank You anyway

 

[missinglinq]

There is some differing of opinions, but a large number of experienced Access developers believe the Compact on Close Property to be bad in that it can cause a db to become corrupted; because of this they believe you should always back up the file before doing a compact, and because of this they never use Compact on Close.

Is this a stand-alone database, or is it used in a multi-user environment? If the latter, it is really necessary to configure it as a split database. Having multiple users sharing a single, non-split database, sitting on a network drive, or using a split database, but having them link to a single Front End, on a network drive, is the sure way to repeated episodes of corruption, speed and timing problems, and all manner of strange, odd and curious behavior.

Multiple users simply have to work off of a split database, with each user having their own copy of the Front End, which contains everything except the data/tables, on their respective hard drives, and a Back End with only the Tables on a shared drive.

Being in forced retirement, I spend 8-10 hours a day here and on other Access forums/newsgroups, and over the past eight years have seen literally dozens and dozens of reports of non-split databases, or split databases, using links to a single Front End, causing these kinds of problems as well as massive data lose! The really insidious thing is that a non-split app can work for extended periods of time before the troubles begin! But once it does, they become chronic, which is to say they occur over and over and over again!

Linq ;0)>

The Missinglinq

Richmond, Virginia

The Devil's in the Details!