>Hasn't done that since 6.0 I think. Having said that the Documentation still lists 'SET STEP' as a command unavailable at runtime. 'SUSPEND' still causes an error.

Hmmm...sounds like the MS VFP team is working to tidy up the debug-code issues, but they are not quite home yet :-) Well, it's not a real critical issue, in their defense...

V.6 sounds right for the last version with a SET STEP ON error, that was the code that bit me the most. A few years back, I several times released EXEs in small, non-critical apps and/or larger-app test versions, with the "forgotten" debug code included. After getting calls from users about the "Feature Not Available" errors several times, I became very careful about leaving troublesome debug code around - so I probably would not have noticed a fix in vfp7 (or 8).