Access 97 Aborts with Windows XP

  • Thread starter Thread starter jk
  • Start date Start date
J

jk

We've been running our Access 97 application on NT
without any problems. The same application that worked
fine on Windows NT does not work consistently on Windows
XP. The error usually occurs when opening or closing a
form and aborts Access.

I'm not sure if it's a memory issue or what???

Thanks for your help!
JK
 
While a97 is rather old (at least 3 office versions old), and it existed
long before win2000, or even winXP, it does run well on winXP boxes.

I have run a97 on many win XP boxes, and it was rock solid for me. Complete
trouble free.

I would make sure you have installed the office updates and also the updates
to JET. (I would assume that was done anyway..but it is something I would
check).
 
jk said:
We've been running our Access 97 application on NT
without any problems. The same application that worked
fine on Windows NT does not work consistently on Windows
XP. The error usually occurs when opening or closing a
form and aborts Access.
Click to expand...

So what's the message?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
The error message is as follows:

"Microsoft Access has encountered a problem and needs to
close."

AppVer 8.0.0.4122
Modver 0.0.0.0
Offset 012df611

Another error showed the following details:

AppVer 8.0.0.4122
Modver 0.0.0.0
Offset 48850b9b

Thanks for your input.
 
The error message is as follows:

"Microsoft Access has encountered a problem and needs to
close."

AppVer 8.0.0.4122
Modver 0.0.0.0
Offset 012df611

Another error showed the following details:

AppVer 8.0.0.4122
Modver 0.0.0.0
Offset 48850b9b

Thanks for your input.
Click to expand...

Unfortunately those are too generic so I don't have a clue. No hits
on the offset either.

I'm wondering if your video driver is up to date. Maybe it's too up
to date. I was having problems with one video card when I had the
latest drivers installed. I uninstalled them and installed the latest
Windows Certified drivers they had which were about six months or a
year older. And things run much smoother.

But that's just a guess.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
jk said:
I'm not sure if it's a memory issue or what???
Click to expand...

My experience with bad memory has been the following although the
message may be slightly different as that was Windows 2000.

Application Error "The instruction at "0x12345678" referenced memory
at "0x90abcdef". The memory could not be "written" which decompile
fixed. Where the eight digit numbers were different each time I
started up the MDB or at random times when working with the MDB.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Back
Top