Repairing database corruption
Posted on 2013-01-23
I've been developing this Access 2007/Sql Server application for 3 years now. The .ACCDB file for the program is 90 meg. Maybe once a month access crashes while I am in the middle of doing something. I know all too well that although I can re-open it and continue working, but the next time I publish a .ACCDE, the user will get an error saying something about an expression that could not be found.
I have the cure for this. Sometimes I just need to repair/compact the database. Then re-publish the .ACCDE. Other times this is not sufficient and I need to decompile the database also.
So I was wondering..... Is there a preferred sequence of doing this? Should I repair and compact first before decompiling? Or should I decompile first, and then repair and compact?