Access Database Is Corrupt - Unrecognized Database Format 1

[Bill6868]

One of our Access databases would not open today. I got the following Access dialogue box:

Unrecognized database format 'P:\AEC-CREO\SigActs\SigActsDatabase.accb

I had a back-up copy on an exterlal drive and replaced the file, so no lost time.

All of our other Access databases opened just fine.

My observations:

1. First I tried fixing it by creating a new blank database and importing all the objects from the corrupted file. This would not work because the corrupted file was unrecognizable.

2. This is not the first time something like this has happened. Although this is a rare occurance.

3. Access does some crazy things from time to time.

Would anyone be able to shed some light as to why something like this happens?

No new data had been entered into the database, so swapping the corrupted file with my back-up file was no biggie. But this could have been a disaster if lots of new data had been entered - I would have lost it all. I'm diligent about making frequent database back-ups as snapshots in time.

Could this have something to do with our network and not Access itself.

I dunno. Any comments would be duly noted. Good grief!

Thanks,

Bill6868

 

[kjv1611]

What version(s) of Access are involved? Do you have Access 2007/2010 yourself?

Reason I ask is that I recently ran into an odd case on a couple databases. I'm using 2010, and some of the other folks 2007. Well, I BUILT the database using 2010, no issues. Then they requested some other chnages, which I made... and proceded to compact and repair.

Well, the "new version" of the databases (split - front/back ends) would no longer open on the other machines, giving the same error. I narrowed down the culprit to a particular userform... and then went back, did all the other stuff, and manually re-imported the problematic form, did NOT compact/repair, and smooth sailing.

"But thanks be to God, which giveth us the victory through our Lord Jesus Christ." 1 Corinthians 15:57

 

[Bill6868]

Thanks kjv1611

We are using Access 2007. The database was created in Access 2007 and not converted from an earlier virsion, and we are still using Access 2007 to open it. The db is not split bewteen front and back ends.

I could have committed some egregious error in my programming/VBA code, but we have been using this database for a couple years now with no problem.

I dunno, maybe just one of those crazy Access anomalies that occur from time to time.

Thanks for getting back with me. If anyone has any further insights please me know.

Bill6868

 

[kjv1611]

Here's a good reference regarding Access 2007/2010 databases - in case it might give some insight. I know one thing is important to turn off the Name AutoCorrect..

http://allenbrowne.com/bug-03.html

Well, that's on the Name AutoCorrect, but from there, you can find plenty other good tips. But that one in particular can cause a lot of headaches.

It's under File/Office Button - Options/Access Options - Current Databse - Name AutoCorrect - near the bottom of the Current Database options

"But thanks be to God, which giveth us the victory through our Lord Jesus Christ." 1 Corinthians 15:57

 

[Bill6868]

Thanks kjv1611. Some interesting perspectives to ponder.

Like I said, Access does some strange things sometimes, that's why I have multiple back-ups - database snapshots over periods of time.

Bill6868

 

[ColdDay]

Same issue, but with a small twist.

I emailed a DB from home (2010) to work (2007). Received the error message when tried to open at work. Followed suggestions found here and at Allen Browne's re: Name AutoCorrect. But my issue is that when I try to import the db into a new blank db per the following instructions, I get the same error.

From Allen's site"
"If you have existing databases where this feature is on, consider creating a new (blank) database, turning it off, and then importing all objects from your existing one (File | Get External | Import)."

Is there another way to work around this issue? Anotehr way to import?

Thanks.

 

[kjv1611]

ColdDay,

For your specific issue which is a little different from the original question, I think all you need to do is:
1. Open the same DB at home again, Convert it to .mdb format, THEN send to work.
2. Now, at work, open with 2007, and if you want in accdb format, convert it back to accdb format with an Access 2007 machine.

I had the same thing at work, b/c one or two machines, they were afraid to upgrade at all, and they were using Access 2007. Well, I created a new database for them in Access 2010. Initially, it worked, no problems.

Then, there was some problem (not related to versions of access), and I repaired the database - compact and repair. After doing so, the users with 2007 could no longer access the database.

How I got around it was just converting the whole thing back to mdb, since everyone's machines could handle that, and problem was solved.

"But thanks be to God, which giveth us the victory through our Lord Jesus Christ." 1 Corinthians 15:57

 

[MazeWorX]

bill6868 It may be an issue with how certain users exit your db corrupting your data. And if you haven't setup a scheduled task for everyday to backup your db, You can run access with a switch to run a macro. In turn the macro can run a function that backs up your db. Done this way it can be unattended or you can use backup software. Every day I backup my db's at midnight. Just an additional thought is your db split?


HTH << MaZeWorX >> "I have not failed I have only found ten thousand ways that don't work" <<Edison>>

 

[genomon]

Here is my last resort when all else fails:

http://www.granite.ab.ca/access/decompile.htm

Beir bua agus beannacht!

 

[MajP]

I assume this is a split database with the backend on the server and all users having a local copy of the front end. If it is not employed that way, it is incorrectly employed and likely the cause of the corruption. In other words if the database is not split or you are sharing a datbase in the network, that is why it is corrupt.

 

[ColdDay]

KJV,

Sorry for the delay in getting back to you. Your suggestion worked perfectly!

CD