>We have been receiving numerous C0000005 errors on Windows 2000 Pro computers. The computers are running Windows 2000 Pro, SP2, and have 256k memory. Our application will semi-automatic process claims in batches of 50. If the computer doesn't need human help, the screen refreshes and moves along as if a person was actually typing the data in. Whenever we receive the C0000005 error, the same four temporary work files index's get corrupted. The error occurs on different line numbers, and on which claim it dies on is also inconsistent. One thing in common, is that all the lines numbers have this code referenced:
>
>IF VAL(m.howaccess) > 0
>
>
>The application doesn't seem to have this problems on Windows 95/98 machines. Can anybody help me find the needle in the C0000005 haystack?
>
>Thanks in advance!!
The most common causes are outdated/buggy video and printer (HP, some Epson) drivers.
On the Wiki:
http://fox.wikis.com/wc.dll?Wiki~C0000005ExError~VFPYou will also find many threads here if you do a search.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
