Corrupted database. Recovery possible?

[ollyb303]

This is a long shot...

While I was working on an Access 2000 mdb today (using 2002, but 2000 format), Access unexpectedly closed itself (I have no idea why, I was just running a fairly standard query). When it tried to reopen the mdb, I get the message that it is corrupt - specifically:

"Microsoft Access has detected corruption in this file. To try to repair this corruption, first make a backup of the file. Then, on the tools menu, point to database utilites, then click compact and repair database. If you are trying to repair this corruption then you will need recreate this file or restore it from a previous backup"

I immediately backed it up, ran Compact and Repair - this threw the same message. I tried creating a new mdb and importing, same message. I tried decompiling from the command line, same message. I have downloaded and run the Jet Compact tool from Microsoft - this failed.

I have had partial success using Stellar Phoenix Access Recovery - using this I managed to recover tables and queries, but NOT forms, reports or modules.

My manager has contacted a recovery service online and sent them the file and they say they can only recover the same.

Our server support team have just told me that the daily backups on the server I'm working on haven't been happening for a few months now (something I was not aware of and unfortunately was depending on in case of a problem like this).

TBH I feel sick - this represents about 2 or 3 months of work!

Is there any hope at all?

[FishVal]

... this represents about 2 or 3 months of work! ...

Not true.

According to my experience recoding the same you've already coded from scratch gives you a better code within less than 1/5 of a time it has taken before. :D

To say nothing about 1-month development log on bytes.com

[ollyb303]

Fair comment.

Is there no hope of recovery then?

[FishVal]

You could wait until Messiah come and ask him to resurrect your application.
:)

Seriously. Being on your place, I would be happy having rescued data.

[ollyb303]

Thanks for answering.

I'll write some code while I wait for the second coming then!

[FishVal]

Even more seriously.

I don't want to help you to bury your Hope. However, I didn't ever see or hear about an mdb recovered after such corruption.

[ollyb303]

Thanks FishVal. I thought that would be the case.

Bugger.

[ramprat]

Here is something I did to recover from a similar situation. Simply open the database using Excel. Choose all files as the file type and then click on the corrupted database. It should then show you a list of tables in the database. You can then save each one in Excel and then reimport them into a new database. I hope this helps. Good luck.

[ollyb303]

Thanks ramprat. This did work to recover the table data. However I had already been able to do this using stellar phoenix.

TBH the tables are not the issue here as the application is actually a front end for an Oracle database so the only tables are a few temp tables with very little data in them.

The bits I can't recover (forms, reports and code modules) are the bits I really need!!!!

I've started recoding it all this morning.

[tdw]

A corrupted database is what caused me to start learning Access.
So far, just self-taught, but may go to school to learn more soon.
No corrupted databases since then....yet....I hope I didn't just jinx myself.

When the Messiah comes, won't the anti-christ be killed?? Without Bill Gates, what would you need with a Microsoft database anyway? So much for Him resurrecting the file.

[NeoPa]

It's avery long shot, but try opening Access and hitting Alt-F11 (to open the VBA window) twice (back into Access). Now try to open the corrupted database using the bypass key (Shift). If you are very lucky it will succeeed to a degree and allow you to switch back across to the VBA window and copy all your code.

If I'm honest I doubt it'll work, but good luck with your attempts anyway :)

[ollyb303]

Thanks for the suggestion NeoPa.

As you predicted it didn't work! But thanks all the same : )

As FishVal predicted, I am progressing much faster than I did with the code originally, the code is tighter and the whole thing is looking improved so far.

I'm making incremental backups every few hours this time!

[NeoPa]

@ollyb303
LOL. I expect it was worth a try anyway.
@ollyb303
I'm very pleased to hear it. Bright sides make life more bearable ;)
@ollyb303
Indeed :) Been there. Done that.

It hurts, but it also changes the way you work to a better approach (although I also appreciate you had it covered as far as you knew).

Anyway, best of luck.

[ollyb303]

: )


Cheers! It's all going well now...

[trixxnixon]

@FishVal
re coding is good practice.