By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,804 Members | 1,634 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,804 IT Pros & Developers. It's quick & easy.

The memory could not be "written".

P: n/a
Hi, there,
I have a simple MS ACCESS application. It supposes to print one
report. It works fine in my computer, it also works fine in some other
computers, but it stops working in one of the computers. When I click
the button which supposes to activate the report, nothing instead an
error messages comes up
'The instruction at "0x77fcb397" referenced memory at "0x491acfb8".
The memory could not be "written"'
I even cannot open any of the reports that I made. But tables and
forms works fine, I mean I can open them without any problem.
Did anyone have this kind of experience? How did you solve it?
Thanks a lot in advance.
Pablo
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
pa*****@hispavista.com (Pablo) wrote:
I have a simple MS ACCESS application. It supposes to print one
report. It works fine in my computer, it also works fine in some other
computers, but it stops working in one of the computers. When I click
the button which supposes to activate the report, nothing instead an
error messages comes up
'The instruction at "0x77fcb397" referenced memory at "0x491acfb8".
The memory could not be "written"'


I've personally seen msaccess.exe - 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.

Decompile would fix this problem but only temporarily.
http://www.granite.ab.ca/access/decompile.htm

(Several months later.) 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.

There have been comments indicating that memtest86 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.

(Several months even later). This problem must have been caused by the bad RAM as
I've never gotten the message since the RAM was removed and replaced. (2003-10-29)

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
Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.