>>One of my guys had this today (he had it about six weeks ago too). The line of code which 'fell over' was incrementing a form property by one - it has worked fine before.
>>
>>What he did was to retype the line and then delete the offending code. It seemed to work - may be a coincidence though!
>
>This one fails only as Foxpro runtime is closed down on one app only, which uses an ActiveX component. Others are fine.
>
>(Ed - I didn't mention the ocx did I. It's a Socket/X from Mabry - no reason to beleive there's a problem with the control.)

The fact that other VFP6 applications on the same machine shut down safely makes the DCOM answer suspect; if it were the generic DCOM error, all VFP6 applications that started up with the screen disabled and were shut down after showing a window would C0000005 out. So something other than the DCOM problem may be causing this particular error for you.

Does the application fail with the C0000005 error if the form containing the Mabry ActiveX control is never instantiated? If not, then something going on in that particular form may be causing the failure.

Does the application fail in the same way if you shut down via different methods (invoking shutdown by clicking the close button on the main window vs selecting an exit oiption from a menu or toolbar)?

Posting your ON SHUTDOWN procedure and the Destroy Event and Release Method code might help here if you suspect code in the form or VFP termination.

Ed