>Perry and Kile,
>
>The C0000005 error is NOT from VFP it is from windows and it means that windows is hosed. Windows memory has become kaka (that's a technical term).
>
>Perry is right, SP3 for VFP6 removes amany of the C5 errors.

Ultimately, the VFP C5 error is caused by a VFP bug. What typically happens is:

- a VFP bug causes VFP to try to access some part of memory it doesn't own
- the computer's CPU (in protected mode) doesn't allow this and coughs up an exception
- Windows traps this exception and reports what happened.

This is a serious error and can't be corrected. Rather than allow the offending program to run and overwrite some other process's resources, Windows' only option is to blow the offender away. Immediate capital punishment - judge, jury, and executioner. So, bye-bye VFP.

Not so nice for your program, but it keeps the OS running.