Software

Ask something
Discussion Locked

Access 97 blows up

0 helpful
12 replies

by john_wills 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

The instruction at "0x022f0697" referenced memory at "0x515eae11". The memory could not be "written".

This happens sporadically. The debug button leads merely to termination. What to do? There is no similarity I can see among the ocasions at which it happens.

12 replies

by dklippert

This from one of the forums:

http://tinyurl.com/6ddn

You could try decompiling:

"full path/name to msaccess.exe" /decompile "full path/name to mdb"

by john_wills

The programmer in tinyurl is losing data; I merely have to restart the database. The obvious source of the problem is hardware, but I have run some hardware tests. The next is Windows, which is perhaps corrupted, but I do not know how that might be tested for this kind of problem. The addresses are not always the same. I cannot decompile as you suggest because the Run command does not like the blank in one of the names("Program Files") in the path to my msaccess.exe.

by dklippert

Surround the path with quotes.i.e.

"c:\program files\blah blah.exe"

What version of Windows are you using?
Have you made any recent hardware changes?

by john_wills

Makes no difference - I already had quotes around "program files" and expanding their range did not get around the problem.
Windows 2000
No recent hardware changes; there are varieties of the error, and some of my colleagues have similar things on their PCs. We are inclined to blame Windows.

by mjmrozo

The source of the problem could be Windows because sometimes Windows just happens to crash at the right time and at the right moment. It could be when you are trying to save data or it just happens sporadically.
One solution to the problem is thatyou might want to check the integrity of the database to make sure that you can store new data in the tables and not get an error message when you save the data. You might also check to make sure that all of your fields, field types, field sizes, etc., are what you want.
If the integrity of the database is fine, try re-naming the database to a different name and running the database with the new file name.
If it works fine in both cases and the integrity is fine then the next solution is to try different operating systems. This will allow you to get different feedback from the particular OS that you are running the database.
Are you using it in a stand-alone environment or are you using it in a client / server environment?

by john_wills

The problem has occurred in several constellations of program etc. I first found it in Access 97, and that is where it has turned up most often, but it has also broken other programs.

by tony

it looks to me that you may have faulty memory chips in your PC.

I would try swapping htese and trying again.

Regards,
Tony

by john_wills

Actually, it did help me slightly, nd I am going to show the page to the IS suport people, but the Microsoft article is about XML, which cannot be the problem in my case, because there is no Net reference involved.

This discussion is closed to new replies.