>If you create an APP that has its own custom HELP file you can issue
>
>set help to mynewhelp.hlp
>
>when the program starts up and everything works fine. Then when the APP exits (on the development PC) you can issue
>
>set help to
>
>so that the default fox help is available to continue development assistance. I usually place this latter line in the destroy event of the main form so that it executes when I shutdown the test run. This practice however creates a problem when the APP is deployed because the
>
>set help to
>
>command looks for the foxhelp.chm file which dosen't exist on the users PC. Is there a better way to deal with this? I suppose it could be trapped with an error handler but that seems like overkill.
>
>Thanks for any ideas.

I use what is probably poor programming technique, but works for me.

I have an environment variable on my development machine. Any code that is supposed to work only on the development machine is wrapped in a IF block

IF GETENV("whatever") = "whatever"
     DO mycode
ENDIF

Not cutting edge but it gets the job done.