Hi, Larry,

I'm surprised I did not think to check that. OK, I cleared the debugger configuration back to default. I'll see what happens over the next few days.

Thanks for the tip.

JME

>Hi,
>You may have a corrupt configuration in your debug enviroment. From the Command window, issue a CLEAR DEBUG. That will return the debug environment to the default settings. You will then have to open and configure the windows back to your settings.
>
>HTH.
>
>>Hi Mark,
>>
>>Yes, that's what I do now. I was just curious if anyone had experiences the same problems and had found a solution rather than a workaround.
>>
>>Appreciate the response.
>>
>>JME
>>
>>>Don't use STEP ON. Go to the line of code, right-click and click on SET BREAKPOINT. You can also use the ASSERT command [see VFP help and use with SET ASSERTS ON command].
>>>
>>>
>>>>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.