A2K database crashes in 2003

TinkerMan

Dooh!
Local time
Today, 10:11
Joined
Jan 12, 2005
Messages
35
My frustration is definitively on the way up, as A 2003 keeps crashing, without giving me any clues as to why.

I have an A2K database (actually 3) split into FE/BE. Works like a charm with A2K and A2002(XP), but I'm having serious problems with A2003.

First off; does anybody know how to debug/get out more information when access crashes ?? is it possible to switch on some debugging or logging? The error message I get, I guess is a generic and common one in 2003: "Microsoft Access has encountered a problem and needs to close. We are sorry for the inconvenience." yeah right!

Under the "What data does this error report contain" there is a shitload of information, mostly in Hex, about 25 modules and the whole stack. Anybody volunteer to decipher it for me :)

Is there an alternative source which does not give me the state of almost the entire machine, but something a bit more narrow, that will actually give me an idea of what kind of error it is, or something that can shed some light on what is going on.

These are my other findings:
- My other two databases seem to work without problems!?!?!
- If I connect by using the original development workgroup file, I cannot even display my menu form!
- I have tried re-creating my workgroup files in 2003 without any resolution
- I have experimented with the "SandboxMode" without any resolutions.

Is there a definite way of knowing whether Access has SP2, where does it say?

I'm not asking you to answer to all my points; anything will be appreciated, as I'm really starting to fumble around in the dark....

I'm using Win XP SP1. A2003 has macro securit set to low.

Cheers
 

Users who are viewing this thread

Back
Top Bottom