>>I am testing a standalone application (which works in the interactive environment) with two users accessing the databases. Occasionally, I get the message "Feature is not available" This is not comming out of my error handler. Anyone know what generates it?
>
>Usually I get this when I forget to take out a SET STEP ON command before building my executable.

Instead of using SET STEP ON, you can also use ASSERTs [ASSERT 1=2 will automatically add a DEBUG option to the error dialog box that this generates as long as you SET ASSERTS ON first]. You can use any expression that evaluates to a logical for the ASSERT expression.

You can also use DEBUGOUT expression which will output the expression to the Debug Output window in the debugger. What is nice about DEBUGOUT is VFP ignores these lines under runtime. So you do not have to remember to remove them.

ASSERTs are ignored at any time with SET ASSERTS OFF. By default ASSERT is OFF. Just SET ASSERTS ON in the command window. If you need to put it in actual code:

if version(2) = 2  && development mode
   set asserts on
endif