Hi,

>>Haven't actually tested this for a year or two, but that's the way it used to work...

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.

Probably not a good habit but I often leave a 'SET STEP ON' in error routines to simplify debugging...

Regards,
Viv