>I see now. I had thought that this (CONFIG.FPW) was something that I would set-up on the development machine and the compiled EXE would be affected.
>
>Re: take an existing executable that doesn't have a CONFIG.FPW, and put this CONFIG.FPW in place
>
>I did this and it shows that it is running as a process in the Task Manager.
>
>I added the _SCREEN.visible = .T. line in the program in the appropruate spot and it works as desired.
>
>Where is this documented in Help?
>
>Also, I have an opinion about this CONFIG.FPW stuff: This is dangerous. All someone has to do is create a CONFIG.FPW file and screw things up. I have a CONFIG.DBF that I distribute with my EXE to set machine/directory-specific settings. I can encrypt the fields for security. CONFIG.FPW is not and cannot be encrypted (right?). This is a little scary.

The CONFIG.FPW is usually compiled into the executable and, therefore, cannot be tampered with after distribution.