How to stop Access 2003 crashing with fatal errors during form des

[Guest]

Access 2003 crashes with a fatal error (very apologetic) and asks me if I
want to repair and reopen. Once this starts happening it keeps happening
every 5 minutes. It seems to me mainly as I am doing a copy/paste in design
mode on a form or just when moving controls. I thought it was just my
Notebook but am having the same problem on my new Notebook. It also happens
with different databases. I have tried decompiling, compacting, etc. I think
the problem only started after the last 1 or 2 Office updates.

I am running XP Pro SP2, all the latest service packs for both the OS and
Office. I also have Access 97 installed and it still works like a dream.

Is anyone else having the same problems or have any solutions?

 

[Allen Browne]

Kevin, there are so many possible causes for this.

A good place to start might be:
Preventing Corruption
at:
http://allenbrowne.com/ser-25.html

After confirming that none of the first items apply, work through the 12
items in the "development" section.

 

[Guest]

Allen

Thanks for the advice. I am already doing most of what you suggest - I have
been developing in Access since version 1.

These errors have only started in the last couple of months which is why I
suspect a Microsoft bug fix is the culprit. It has now happened to me on 2
different Notebooks, the latter a new machine (2 weeks old). It also happens
even when changing backend databases (only tables and a few queries but no
forms).

I am getting very frustrated, not to mention wasting a lot of valuable time
continually restarting Access, saving, compacting, etc.

Regards
--
Kevin Seerup
GoalMaker Pty Ltd
http://www.goalmaker.com

Kevin, there are so many possible causes for this.

A good place to start might be:
Preventing Corruption
at:
http://allenbrowne.com/ser-25.html

After confirming that none of the first items apply, work through the 12
items in the "development" section.

 

[Allen Browne]

So you have Name AutoCorrupt turned off, you have decompiled, etc.

Is there a scenario that tends to trigger this?
A particular query, or type of query?
A particular form or subform?

 

[Guest]

I have name autocorrect off, have decompiled, etc. It seems to happen
primarily during form/report design, often just as I do a copy/paste or drag
a control. It doesn't seem to be subform related - it happens even where
there is no subform.

The key thing is that it seems to be happening on a number of the databases
I develop for clients but it has only been happening on these databases for
the last couple of months. I am hoping Microsoft will finally realise where
they have stuffed up one of the recent Office updates. The message logged to
the Event log (Event ID 1000) doesn't yield any useful info. One example
follows:

Faulting application msaccess.exe, version 11.0.6566.0, stamp 42cdb33e,
faulting module msaccess.exe, version 11.0.6566.0, stamp 42cdb33e, debug? 0,
fault address 0x00033cdd.

Regards

 

[Allen Browne]

Can't say I recognise anything similar to what you describe, Kevin.

I do not experience anything similar to what you describe, and I am mostly
developing in Access 2003 SP2 also. (On Win XP SP2 if it makes any
difference.)

If it happens on many forms in different databases, it is unlikely to be
related to a corrupted database. Dragging controls is video-related, so
could be the result of a flawed video driver. If your 2 notebooks have
different video drivers, it would make that idea less likely.

It could also be related to other software running in the background (e.g.
if you run the same antivirus or screen saver on both notebooks.)

If you are using Windows XP, you might try switching the theme to Windows
Classic, just to see if it makes any difference.