This is what I ended up doing, embedding logging of user steps. But I forgot about the #IFDEF, as you suggested. I used to use it in my Clipper apps and it would be useful in VFP too, especially much easier to clean up the test code.
Thank you very much for your help.
>Hi,
>
>You're best option might be to embed some type of logging mechanism in your base classes. Of course the problem is that you're logging a huge amount of information whether there's an error or not. You could compile both a normal version and a 'debug' (#IFDEF DEBUGGER... #ENDIF) version of the app for use when necessary.
>
>HTH,
>Viv
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
