I agree. Here's what I use instead of SET STEP ON:

ASSERT .F. MESSAGE [SET STEP ON]

This is guaranteed to not break your app at runtime, but accomplishes the same thing during development.

- Bruce



>>>Hi,
>>> I have a class in prg file. I have difficulty to debug it becoz debugger doesn't stop at the breakpoint i specific. How?
>>>
>>>Thank you
>>
>>Sometimes I had the same problem.
>>
>>Just insert the command "SET STEP ON" before the command you want to debug.
>>
>
>SET STEP ON will work, but it's ugly. One of our nightmares is a forgotten SET STEP ON somewhere in the code, which will break with an ugly "feature not available" error in the .exe - a far better solution is to ASSERT {lCondition} in the code, and have Set Assert On while developing. It does nothing in the .exe, and you can always Set Asert Off while testing. Assert also gives you a dialogue box which pops up if lCondition is false, so you actually have a conditional breakpoint which is active in development only. I highly recommend it.