>Or better yet:
>
>If _VFP.StartMode = 0 && a development version of VFP
> Set Assert On
>Else
> Set Assert Off
>Endif
>
>At least this way - you do not have to keep recompiling things. So, if a client has a problem, you can get his/her EXE - drop it into your dev environment - and automatically have assertions available. I just don't like the idea of having to recompile to get to a certain state. We have all of these ways to tell if we are in or not in dev mode. Why not use them????


what about having an include.h file with a statement like

#DEFINE DEBUGMODE .T.

This is the method used in the TasTrade example.



and then using DEBUGMODE for SETting the ASSERTION mode and
other debugging features you might have in your app ?


Dave.