Although I concur with the rightclick-set breakpoint method, I have created a little program called stop.prg. Here is the code:
IF VERSION(2)<>0
KEYBOARD '{SHIFT-F7}'
SET STEP ON
ENDIF

RETURN

Because I only ship .exe's to my clients, the code in the IF-statement is only run during development.
I use the Shift-F7 to get back to the call to STOP() not the SET STEP ON in STOP().

As you guessed, this program is called with:
STOP()

And no client will ever see the 'feature not available' from this prg.

Regards,
Frank


>>You should get out of the habit of SET STEP ON. A much better solution is to right-click on the line of code in the edit and select Set Breakpoint from the shortcut menu. It will not carry through to runtime.
>
>I do this, too. The problem is that it doesn't always stop where I want it to, and doing it this way means I have to keep the debugger open until I get to my breaking point. This slows down execution and I don't always have the patience to wait.