Microsoft Office Access Has Stopped Working

[austin3515]

Almost finished with the biggest database I've ever done. There's probably 25 to 30 diferent tables/forms/reports/queries, total, with pages and pages of code.

When I create a brand new database and import all the objects from the "broken" version, that makes the problem go away. Then a few days later, the same problem will come back.

If anyone asks, I did try compact and repair (I do it relatively often).

Also, I just tried to open on another computer, but now the .laccdb file is stuck open so I can't open it...

Wlould any of this be improved by upgrading to 2010?

 

[SydneyGeek]

It sounds like you have a corrupt form or report.

If you haven't split the database, do it; you separate data from logic, which will give peace of mind when this sort of thing happens. Then:

Get into the code environment (Alt+F11) and Debug > Compile. If you get any errors fix them until the code compiles; you now have a stable state for the next step.

Import all objects into a new DB.

Go to this link, which has some useful detail on dealing with corruption. Near the bottom of the page is a link to an add-in that lets you export all database objects as text, then re-import them into a new database.

The text file approach works because it strips out all the compiled meta-code that can get corrupted. You effectively sanitise the forms and reports. Once re-imported the new db should be both more stable and smaller.

Disclaimer: not a magic bullet, but the text file round-tripping has saved my bacon a couple of times.

Denis

 

[austin3515]

I can't wait to try it when I get home tonight. Sounds like a great plan!! Out of curiousity, would splitting the database prevent this issue in teh future?

 

[SydneyGeek]

Not necessarily. But it will keep your data safe.

Make regular backups of the front end; do one before making design changes, for example. Then if it goes belly-up you restore a recent front end backup, and keep going.

Also, if you don't do it regularly, a compact and restore is a useful bit of housekeeping. In Access 2007 it's in the Home button > Manage > Compact & Restore.

Denis

 

[austin3515]

"Get into the code environment (Alt+F11) and Debug > Compile. If you get any errors fix them until the code compiles; you now have a stable state for the next step."

I tried this and, whoa, did I find a lot! There were snip-its of code tied to forms that wre totally unrelated. I think it was my fault because I occasionally will copy a form, and perhaps the code comes with it...

Also, I had a lo of me. references that compile did not like, so i replaced with forms.frmabc.controlname.

At any rate, after fixing all my compilation errors, my database is working again, A-OK. If it breaks again, I'll try the rest of your suggetions.

THANKS!!!!

 

[SydneyGeek]

You're welcome. Debug > Compile is often a good first step.

Denis

 

[austin3515]

hey, I split my database, but now the "table and related view" isn't working. So all my queries, forms and reports, which you used to be grouped with the table to which they were related, are now all listed as unrelated. Can this be fixed?

 

[SydneyGeek]

Can't say I've had that problem before. Switch to one of the other options (like Object Type), then back again and see if that helps. Otherwise I'll run a search and see if anything crops up.

Denis

 

[austin3515]

I had tried all that. After posting I found that once an object was opened, it founds its way home, so to speak. But with a couple dozen objects, that was a pain in the neck!

 

[SydneyGeek]

Must be an 'undocumented feature'... good to hear it's working now.

Denis