>Hi, Upendra-
>Also, I add this command to my (dev time) config.fpw:

step = on

, so the debugger just starts automatically.
>
>A couple of highlights:
>
>You can run the debugger in either the foxpro window or as it's separate window. I like to run it in it's own window so that it doesn't take up screen real estate.
>
>I add a SET STEP ON in new code sections that I want to step through.
>
>You can use the ASSERT command to have the program break if some condition is false. This is useful when you want the program to halt only if something goes wrong.
>
>There is tons of useful info about the debugger, and we don't discuss it enough in the forums, IMHO. Thanks for asking.
>
>>Dear UT user's
>>
>>I would like to know how do we use Debug. I have been using similar debugger in Clipper 5.0 (Language). The sequence there was to start the debugger with the .EXE file from dos command prompt. (e.g. CLD main.exe). Now if we want to run it as normal, we use to press F5 and if we decide somewhere in the middle to get back into debug mode we use to press ALT+D and then F8 to step in step by step or Press F9 as a break point.
>>
>>In the similar manner I would like to know how does VFP Debugger works:
>>
>>1. Is there a way to start a debugger on launch of a form or when we click on a command button etc.
>>
>>2. Is there a way to start a debugger on pressing some hot keys.
>> (for e.g. something similar to clipper)
>>
>>(Upendra Nayak)

You can also start the debugger with the DEBUG command.