>>>>You've just introduced me to a command that I never knew existed. I usually do:
>>>>
>>>>DEBUG
>>>>SUSPEND
>>>>
>>>>Thanks
>>>>Kev
>>>
>>>What I sometimes do is wrap my debugging code in an if statement:
>>>
>>>

>>>IF VERSION(2)  0 && Runtime
>>>     SET STEP ON
>>>ENDIF

>>
>>Hi, James, Kevin.
>>
>>We use a little function called Developer( tcMessage, tlLog ) that tests if wwe are at runtime or not.
>>
>>If we're in development environment, it shows the message, giving the options to suspend, cancel, debug or ignore.
>>
>>If we're in production it just passes by, logging the message to a file if the second parameter is True.
>>
>>It is that kind of stupid functions that you just can't live without.
>
>I know, I know. You can use ASSERT for this, but we started doing this in FPD 2.6, and ASSERT don't allow you to log the message. 8-)

At this point I need to say that too much unneccsary code slow things down. I make it a habbit of removing dubugging information before compiling a final release.