Can you just set a break point? I prefer that over SET STEP ON because you don't have to remember to take out the line of code

It could be a corrupt FoxUser file. Delete yours then try again.

>I've put a SET STEP ON statement inside a command button. When the line executes the debugger appears and then I get
>
>"Microsoft Visual FoxPro has encountered a problem and needs to close. We are sorry for the inconvenience."
>
>I get the same result with ASSERT .F.
>
>I'm sure there is something in the environment that I've set incorrectly. Could somebody give me some idea of what that might be???
>
>(The application is built using Visual Maxframe. I couldn't find a forum for that. My apolgies if I missed it)
>
>Thanks..................Rich