Hi Barbara --

ROFL...skipped a step there, eh? I meant any code that physically comes after READ EVENTS, which implies a CLEAR EVENTS is issued. I just forgot to specifically state this. Thanks for the clarification. BTW, I first ran into this problem when an exe of mine kept bombing on hitting the close "X" and I had ON SHUTDOWN CLEAR EVENTS.

>John, It's a little hard to do data entry without screen I/O. Or do you mean after CLEAR EVENTS?
>
>Barbara
>
>>Jesus ---
>>
>>If you do any screen I/O after your READ EVENTS, it will C0000005 in the executable. CLEAR WINDOWS, _SCREEN references, anything like that will cause VFP to bomb. Check for that and if you find it, remove it. After all, you don't have to mess with the screen with the runtime anyway, just QUIT.
>>
>>
>>>After converting from VFP5 to VFP6, we get a fatal error (C0000005) when attempting to run the executable from outside of the development environment (VFP6), however, the application runs great from within VFP6. Anyone have any ideas? We are all out. Appreciate the help!