Skip to content

Last Resort for Problem Databases

Looks at a method that’ll often fix a problem that’s resistant to all other repair methods.

Q:  Harold Lewton writes:  ” I have 1 database file that works perfectly in Access 2000 and partially in Access 2003. In Access 2003 it works fine while in the Access program itself until I close down the file and then Access crashes wanting to send Microsoft an error message. I have tried converting and repairing the file, all to no avail. Access crashes every time I close out of the file. I should also say that on another machine this same file works perfectly in Access 2003 so I did run a repair on Office 2003 but that didn’t help either.”

 

A:  At first I thought this might be a problem with a digital signature, and recommended trying the fix in KB 823225.  But Harold tried that, and it didn’t fix the problem.  So I recommended the last-resort fix of creating a brand-new database and importing all objects into it – and that worked!  This method, though tedious, will sometimes fix a problem that is resistant to all other repair methods.  I have found it useful when there is an object in a database that I can’t open, delete or rename.  In that case, import all objects except the problem one, and recreate the problem object from scratch.

About this author