Corrupt Database

[adstam]

:-(
I guess this is a hard one. I do have an Access 2000 database that needed some re-engineering. After about 30 hours work since my last backup (writing code, (re)creating forms, etc) my database crashed. Usualy this is not really a problem. Using Compress/Repair would normaly be enough to get on the road again, but......
Every thing i do to get into the database brings Access in a 'not responding' state.

Is there anybody who can help me out....
(our helpdesk is preparing me for the worst)

 

[MaeJams]

We've run into this problem before with Access 97 and the solution we were advised to use is a utility distributed, I believe, in a Microsoft patch called Jetcomp. You may want to search the Microsoft site for this utility/patch. I've found it to be a very handy utility - it works better than the Access based compact/repair utility.

 

[RickSpr]

Does "everything I do..." include creating a new database and importing everything from the crashed one? Often that's the best way to recover from a corrupted database.

Did the crashed database have startup code? I find that sometimes, if I neglect to set my DAO object variables to Nothing before I exit (this is a known bug that causes Access 2000 to refuse to terminate), I'll get hung when I try to start a second instance of Access. If this is your problem, importing into a new database will not copy the startup properties, so you might be able to get in and fix it.

While you're at it, check the Ctrl-Alt-Delete Task List and kill any instances of Access that might be running invisibly. Rick Sprague

 

[adstam]

RJoub
Thanks for your response, I will look for this tool....

Rick
Yes, I tried an import from my objects into a new database, before i got my objects-panel access stops responding.

Because the only way to stop Access I have used the Task List several times. The only Access task in it was the task for the corrupted database.

Ad Stam

 

[adstam]

snif, snif.....

I tried JetComp. Although it seemed that the compress worked fine (it created a new database without any errors) the new created database made Access hung again.

So, I guess I have to take a deep breath and start all over again (with the only advantage that everyting has been done before and therefore I should know the do's and dont's)