>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
>
My preference is to place SET STEP into the code. AFAIK, it doesn't do anything in the executable. Opening the debugger and setting a break point has (for me) the disadvantage that all the code runs in debugging mode and I've seen cases where that is significantly slower.

(I use SET STEP rather than ASSERT because that's the way I've always done it. From what I can see ASSERT is probably better but actually using it is one of the things I will address when I get around to joining Procrastinators Anon)



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

Turns out that fixed the problem. I feel a little silly in not having thought of that as I'm aware that could have been the problem. I just sort of focused on it being a VMP configuration issue where I'm REALLY weak.

Thanks a bunch!!!

..........Rich


>
>>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