>>>You must either include the CONFIG.FPW in your .EXE file,
>>
>>Ed- I have heard people say this before, and never been able to make it work. In my experience the only way to suppress the screen is by actually having the config.fpw in the directory, including it in the project is not enough. Am I doing something wrong?
>
>I think so; I include a CONFIG.FPW with RESOURCE=OFF and SCREEN=OFF in my projects under Other/Text Files where I know I don't have to adjust the CONFIG settings on a station by station basis, and it works great, even when starting the .EXE from a different directory than the .EXE lives in. That's all I've needed to do to get it to work. It works fine, both with top-level forms and where you go and modify how _screen is set up before making it visible. I use this pretty often with apps that are designed as post-setup executables fired from Setup Wizard all the time, as well as a number of tool-type applets.
>
>If I want to be able to do any tuning or customizing of the configuration, I have my setup program construct a default CONFIG.FPW, and then have a menu option in the application that runs a form to guide the user through the tuning process. Since I rarely know ahead of time where the user is going to have space for temporary files, and it's almost inevitable that the setup will vary from station to station in a multiuser environment.
>
>Embedding the CONFIG.FPW obviously -won't- work if you run the .EXE inside the VFP development environment; the settings in the .EXE wouldn't be available until well after VFp has started running and set itself up for things like TMPFILES, MVCOUNT, PROGWORK, etc.

Here are my steps:

1 New Project- proj1
2 New Program- Program1 (MESSAGEBOX("Howdy ya'll") (this is the main program)
3 New program- SCREEN=OFF
4 Rename second program Config.fpw
5 Compile to c:\whatever\proj1.exe
6 go to Explorer, navigate to my new exe, and Doubleclick

VFP window pops up, and then my messagebox appears.

I am currently running VFP 6.0 on Windows NT SP3, but I have observes this same behavior with VFP 5 and Windows 95. What am I missing?