[AccessD] Access97 on W2000 crashes

Hi Andy

Yes, I see the problem. 
But the import thing - if it should be the cure - should really be a one-timer. If it works, proceed evolution on the fresh version as it should work on W98 as well.

/gustav

>>> andy at minstersystems.co.uk 09-01-2006 14:50:04 >>>
Mmm, well there may be a Debug.Print around in a called routine somewhere I
guess. I'll take a look. I've decomp'd and recomp'd on the W2K machine but
not done the new MDB thing. I could try but it'd be a nightmare scenario.
The MDB is in constant evolution and I couldn't contemplate having to do
that every time. Madre mia! Still, I guess it'd be worth knowing if it cures
the problem. Thanks Gustav. Any other suggestions welcomed (very, very
much).

--
Andy Lacey
http://www.minstersystems.co.uk 




--------- Original Message --------
From: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
To: "accessd at databaseadvisors.com" <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Access97 on W2000 crashes
Date: 09/01/06 13:24


Hi Andy

I had a similar thing which I tracked down to a line with Debug.Print.
Commented this out and the code ran, believe it or not.
However, that was not intermittent but consistent.

Have you been through the usual tools: decompile and recompile on Win2000?
Or - still on Win2000 - import all objects in a new file?

/gustav

>>> andy at minstersystems.co.uk 09-01-2006 14:07:32 >>>
Help guys

I have this Access 97 MDB (FE and BE both A97) which has been running for
years, mostly on W98 but also for some time on W2K. Last week something new
happened. 2 users who were previously on W98 went to W2K. They use a part of
the system which others don't, or at least they try to but when they do it
regularly crashes with:

"Msaccess.exe has generated errors and will be closed by Windows. You will
need to restart the program. An error log is being created."