Access 97 errors with Windows2000

[Ray Smith]

On upgrading from Windows98 to Win2000pro I am getting
frequent application errors in Access. I get a message
that an error log has been created but can't always find
the log in Drwatson. Some of the errors say that data
can't be written to certain addresses.
We reinstalled Office 97 after the upgrade and the errors
are still popping up. The database does run over a
network, but the errors are new to Win2000
Thanks
RS

 

[Allen Browne]

First thing to try, Ray, would be service patches.

1. Make sure you have SR-2 for Office97 (see Help | About):
http://support.microsoft.com/default.aspx?scid=/support/servicepacks/Office/97/SR2.asp

2. Make sure you have Service Pack 3 for Jet 3.51:
http://www.microsoft.com/downloads/...88-52ec-4a8f-8bb2-8b06d6cb668d&DisplayLang=en

3. If the server is also Win2000, make sure it has SP3. That's important, as
this patch disables opportunistic locking which has known issues for Access.

4. You are probably not using the ADO library in Access 97, but if you are,
check your version of that also.

After that, the next culprit could be faulty drivers. A faulty screen or
printer driver can cause Access to crash, esp. when opening objects.
DrWatson may be able to give you clues about which module is crashing, or
the timing of the crashes may provide you with clues (what was happening at
the time).

 

[Tony Toews]

3. If the server is also Win2000, make sure it has SP3. That's important, as
this patch disables opportunistic locking which has known issues for Access.

Supposedly. There is the odd report indicating some users still had
to disable OpLocks even with SP3 installed. Also the workstations
have to have SP3 installed as well.

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

 

[Tony Toews]

On upgrading from Windows98 to Win2000pro I am getting
frequent application errors in Access. I get a message
that an error log has been created but can't always find
the log in Drwatson. Some of the errors say that data
can't be written to certain addresses.

Was the message "The instruction at "0x12345678" referenced memory at
"0x90abcdef". The memory could not be "written"? Where the eight
digit numbers are different.

In my case it turns out this problem was almost certainly caused by
some bad RAM up around 891 Mb of a 1024 Mb RAM system. <sigh> So if
you're getting this problem I strongly urge you to use Memtest86 - A
Stand-alone Memory Diagnostic. www.memtest86.com. It worked for me.
Among other things this test can be downloaded as an ISO image which
results in a self booting CDR.

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

 

[Ray Smith]

-----Original Message-----


Was the message "The instruction at "0x12345678" referenced memory at
"0x90abcdef". The memory could not be "written"? Where the eight
digit numbers are different.

In my case it turns out this problem was almost certainly caused by
some bad RAM up around 891 Mb of a 1024 Mb RAM system.

you're getting this problem I strongly urge you to use Memtest86 - A
Stand-alone Memory Diagnostic. www.memtest86.com. It worked for me.
Among other things this test can be downloaded as an ISO image which
results in a self booting CDR.

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
.
Tony,

That indeed was one of the messages I was getting, and the
memory addresses were different. I also got different
addresses on different occasions. Thanks for the tip.
I will check this out.
Ray Smith