[AccessD] Access97 on W2000 crashes

Andy,

Can you post the routine here?

As Gustav noted - debug.print or better custom log file writes here and
there in the problematic routine could help to localize the source of the
problem rather quickly - after not that many GPF crashes hopefully. BTW, do
not forget to "kill" ghost MS Access instances/monikers before the next test
run, which may hang in Running Objects Table(ROT) when MS Access GPFs - use
ROTClean utility for that ROT clean-up...

> It isn't a coding error because everything works fine on W98.
This could be coding problem, which doesn't appear on W98 but shows its ugly
head on W2K with latest updates.
There was a problem with recordsets in MS Access 97 SR1, which was breaking
MS Access 97 (first release) code and then MS Access 97 SR2 solved the
issue. Sorry, I can't remember what kind of problem it was - maybe this link
helps: http://www.mvps.org/access/bugs/bugs0016.htm...

Shamil

----- Original Message ----- 
From: "Andy Lacey" <andy at minstersystems.co.uk>
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
Sent: Monday, January 09, 2006 4:07 PM
Subject: [AccessD] Access97 on W2000 crashes


> 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."
>
> Needless to say no error log is created at all.
>
> It isn't a coding error because everything works fine on W98.
>
> I used the word 'regularly' above because it's intermittent (the worst
> sort). Sometimes it runs fine, other times it crashes, and seemingly at
> different points in the routine. I say seemingly but I'm not 100% sure
> because debugging this is a nightmare. When it crashes it doesn't go into
> debug, so the only way I can see is to step through and wait for it to
> crash, but it's a huge routine and as it doesn't crash every time anyway
> I'll be here til next Xmas trying to see where it fails.
>
> When I Googled the error I found suggestions to reinstall Jet 3.5 SP3,
> reinstall Office SR2B, recopy DAO350.DLL and increase Windows paging
limits.
> So I've done all of those things to no avail. Also it is not machine
> specific. I've gone to another machine running W2K which has been running
> the system for years (but not this are of functionality) and it crashes
too
> when I try this routine.
>
> Has anyone had anything like this (and solved it)? Any bright ideas?
>
>
>
> --
> Andy Lacey
> http://www.minstersystems.co.uk
>
> ________________________________________________
> Message sent using UebiMiau 2.7.2
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com