HELP! Backend > Database format not recognized!

[ick64]

Hello all,

When creating a new table in a back-end database I got a message that the file was corrupted and a backup would be created. After several minutes Access was clearly locked.

Now I do access the front-end files but when clicking on any form or report I get the message:
"Database <back-end> format not recognized"

The backup file it created in the folder brings the same error.

What can I do? Do I have to go back to my own backups to restore the back-end as it was before?


Thanks a lot!

[JoeM]

There are a few options:
- Restore an old backup
- Create a new blank database, and import all your objects (which should just be tables, if it is a back-end) from the corrupted database to this new one

Just note that if you use a new back-end database, you will need to go in to your front-end, and point it to the new back-end (via the Linked Table Manager).

[ick64]

Thanks JoeM for the prompt response!

How can I import the tables to a new back-end file if I cannot open it? When I try, there is a message that the file is corrupt and it will try to create a backup etc but just keeps running and running...(blank screen, Access "not responding" in the title bar)

[JoeM]

You do not need to open it all. You do everything from the new database.

Go into your new blank database, go to External Data -> Import & Link and select the Access option.
From there, you browse to the corrupt Access database, and select the tables you wish to import.
So you never have to physically open the corrupt database to import the tables from it.

[ick64]

Thank you JoeM.

I tried that but, in the new file, after browsing/selecting to import the corrupt Access db, I get the same message when opening the corrupt db itself: MS Access detected an inconsistency and will try to recover it, etc. Then it gets locked.

Is there any other way to do it?


Thanks again!

[JoeM]

No, that has always worked for me before.
You may have no other choice other than to restore the last working backup.

[ick64]

I will do it then - thanks again!

[CJ_London]

Adding a new table should not cause corruption, you should also try to investigate why your db became corrupt - working in a wireless environment for example - and then take steps to minimise that risk for the future.

One other thing to try is to see if you can open it in VBA from another db.

1. Create a new database
2. Create a new module and use this code

Sub OpenDB()
dim db as dao.database

set db=dbengine.opendatabase("...path to your corruptdb.accdb",-1,0,";")

end sub

if that works you can then you should be able to use code to copy the data across. Might be by populating a recordset, then saving to your new db. Might be by using msysobjects, might be by using tabledefs

Note: take a backup of your corrupted db and work off that.