Access 2007 instability/crashing

[Minton M]

Hi everyone,

I've had some issues with a project converted from A2003 now crashing
in Access 2007 after a week or two of dev work. In case anyone else is
in the same boat, here are some of the steps that I took that *seem*
to have fixed the problems.

The symptoms were that I couldn't open the code window without
crashing, nor could I import all the objects into another DB. Please
post any additional tips onto the back of my thread, since I think we
may all be guinea pigs for A2007 at this point!

1. Convert to accdb format immediately.
2. Turn off Name AutoCorrect options (thanks to Allen Browne for that
one.)
3. Split the tables/data and code into the classic front-end/back-end
configuration. This seems to make a big difference.
4. In the code window, turn off 'Compile on Demand' and 'Background
Compiling'.

I couldn't 'rescue' the corrupted mdb, but after making these changes
I have two working accdb files and haven't lost anything. I just wish
the MS Access team would spend some time on the stability of MDB files
- we haven't had a stable version since Access 1997 and it's hard to
justify using these tools in a corporate environment when the
fundamentals are flaky.

James Beswick

 

[AccessVandal via AccessMonster.com]

Hi James,

Thanks for the input on Access 2007.

Is there any macros in your 2003 version when you updated it to 2007? Just
wondering.

I was looking up for Ms Access viruses recently and then your post appeared.

 

[Minton M]

Actually, I studiously avoid macros because I prefer code. But I found
in Access 2007 that they've really swung heavily to using macros in
the control wizards, which I presume must be related to the security
center 'features' on running trusted code.