Error in export of report

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

When we generate a report, and then select the send option. Error 0x77fcc39e referrenced memory at 0x59f71d8. The memory could not be written. Any ideas how to fix this? I seems isolated to a PC. Same option works fine on other PC?

Any suggestions???
 
Most likely a memory problem. Try replacing the memory sticks. (Of course
do the simple things like compact & repair first.)
Nelson

Robert Humiston said:
When we generate a report, and then select the send option. Error
Click to expand...
0x77fcc39e referrenced memory at 0x59f71d8. The memory could not be written.
Any ideas how to fix this? I seems isolated to a PC. Same option works fine
on other PC?
 
It is most likely not a memory problem. Programmers that use lower-level
languages such as C++ can easily get an error such as that and therefore we
know it is a software problem, not hardware.

For MS Access programmers, it is most likely that software is not installed
properly. Another possibility is that something is not installed. Problems
such as this might cause an error code that we can check for but programmers
often don't bother.
 
There is probably more in the message. In particular, there is probably a
".exe" of ".dll" file that is shown in the message. If so, then your chances
of getting useful help will be immensely increased if you provide that
information.


Robert Humiston said:
When we generate a report, and then select the send option. Error
Click to expand...
0x77fcc39e referrenced memory at 0x59f71d8. The memory could not be written.
Any ideas how to fix this? I seems isolated to a PC. Same option works fine
on other PC?
 
To clarify something I said previously, if an error code is ignored then the
memory problem described in the original question can be the result. If
error codes are processed, then at least the program can be ended more
gracefully and with a more meaningful error message.

For MS Access programmers, it is less likely that this is happening, but it
is possible.
 
Sam,

Thanks for the good responces. The only thing that I see is, at the very top of the window. It shows. "msaccess.exe - application error. Now this is the thing. It only happens at this work station. I can go to another work station and no problem.

Any thoughts?

Thanks
 
These things are among the most difficult to debug. You can save a lot of
time by looking at the code as closely as you can. Unfortunately it is
unlikely anyone can help unless you know what the cause is. Of course, if
you know the cause, then you don't need help.

And again, it is especially important to ensure that any error that might
occur is detected and that a reasonably meaningful error message be shown
and then the program should exit as gracefully as possible. It can really,
really help also if the error message includes something to allow you to
determine where in the program the problem is occuring.

If it is relevant, it might help to single-step through the code. Are you
familiar with doing that? That would be relevant I think only if you have VB
code, but if you do, then single-stepping might really help.


Robert Humiston said:
Sam,

Thanks for the good responces. The only thing that I see is, at the very
Click to expand...
top of the window. It shows. "msaccess.exe - application error. Now this is
the thing. It only happens at this work station. I can go to another work
station and no problem.
 
Back
Top