There are more debugging features in the development mode that might help isolate or localize the C0000005.

Some of us have even posted code that will generate a C5. Example: A remove object (a child [container] of a form) has focus, a C5 will be raised. Howver, when the parent has focus, the C5 remains mute.

By running the FXPs inside VFP, you can isolate the point of C5 and work backwards. Usually things can be re-arranged to prevent the error.

I am not suggesting your customer purchase VFP. I have my customers purchase a license - but it is rarely installed. But you could install your license just to localize the C5 issue - a workaround or configuration change usually takes care of it.

>These are test machines designed to be running the exe without VFP installed. (distributed exe)
>
>Before I try your suggestion, could you tell me how this would help in determining the problem? Just curious...
>
>I would put money down that your suggestion would take care of the problem, but it may not be practical to require a customer to purchase a copy of VFP 8 to get the software to run. I don't want to buy a copy for them in each instance either... <bg>
>
>
>
>>What happens when VFP 8 is installed on the machine and you run the app from the command window or project manager?
>>
>>>I have a case where an exe compiled in VFP 8.0 SP1 is giving this error when I try to run on a couple of win2000 machines...
>>>
>>>The exe will not continue, and the log file contains the following info:
>>> Fatal error: Exception code=C0000005 @ 03/04/04 11:45:13 AM. Error log file: K:\ub\VFP8Rerr.log
>>>
>>>I have the 8.0 sp1 files in the application folder
>>> msvcr70.dll
>>> gdiplus.dll
>>> vfp8r.dll
>>> vfp8renu.dll
>>>
>>>These machines both have 6.0 sp3 runtimes installed and will run app files compiled in 8.0?
>>>
>>>Let me know if I can include any other details that may help...