MSACCESS.EXE - Application Error

[Heather]

I had tried posting this message yesterday, but when
trying to search for a response, I couldn't find my
original message.

I receive the following error message when creating
reports in Access 97. The message always shows up if I go
back to the report details page to change the report
criteria and create more than 2 reports:

[reports] MSACCESS.EXE - Application Error
The instruction at "0x1926bf20" referenced memory
at "0xffffff84". The memory could not be "written".

And then access shuts down. Do anyone know what the
problem is, or if there is any way to stop this? Thank
you!

 

[ttoews]

I had tried posting this message yesterday, but when
trying to search for a response, I couldn't find my
original message.

I receive the following error message when creating
reports in Access 97. The message always shows up if I go
back to the report details page to change the report
criteria and create more than 2 reports:

[reports] MSACCESS.EXE - Application Error
The instruction at "0x1926bf20" referenced memory
at "0xffffff84". The memory could not be "written".

When I had this problem it turned out to be bad RAM. Try running
Memtest86. There have been comments indicating that it sometimes
shows problems which don't exist according to some technicians. OTOH
I've run it overnight on some systems and haven't located any problems
which weren't there.

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]

I had tried posting this message yesterday, but when
trying to search for a response, I couldn't find my
original message.

I receive the following error message when creating
reports in Access 97. The message always shows up if I go
back to the report details page to change the report
criteria and create more than 2 reports:

[reports] MSACCESS.EXE - Application Error
The instruction at "0x1926bf20" referenced memory
at "0xffffff84". The memory could not be "written".

When I had this problem it turned out to be bad RAM. Try running
Memtest86. There have been comments indicating that it sometimes
shows problems which don't exist according to some technicians. OTOH
I've run it overnight on some systems and haven't located any problems
which weren't there.

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