>>>Hi Dragan,
>>>
>>>>Works most of the time, except sometimes :). IMO, Set Step On is something you'll forget. Set Assert on somewhere in the beginning of your app, and Assert .f. will pop up better than Set Step on, because it will ask you what you want to do. Good thing is that even if you forget to take it out, it won't come up in production: Assert doesn't work in an .exe, so it won't break with 'feature not available' like Step or Suspend would.
>>>
>>>The foxteam has changed this behaviour in VFP7. Instead of 'feature not available', it will not ignore SET STEP ON or SUSPEND commands.
>>
>>They have a beer for this.
>
>Finally, the Foxteam became aware that we, VFP programmers, are human after all and forget where we put all those SET STEP ON or SUSPEND commands, untill the client got the infamous 'feature not available' message.
>
>They get a Six-Pack from me for this one.

On my side, I am aware that Foxteam are human as well... and if they ever got all the beers they deserved for this, we'd never see VFP8 :)