Having installed SP3 I am generally pleased with the fewer C5 errors, but unhappy that any C5 error leaves an instance of VFP in memory with no handle and no way to close the session except by restarting Windows (At the moment I am completely at a loss for the words necessary to thank Mr. Gates for his wonderfully stable operating system!)

Much to my surprise, most C5 errors seem to occur when I put a "set step on" command in code to initiate a trace. The error occurs on the next line in code following the "set step on".

(1) Does anyone know of a means of preventing VFP sessions from hanging when a C5 error occurs, and

(2) Does anyone know of a way of invoking the debugger without risking a C5 error?

Any assistance would be greatly appreciated.

Many thanks.