>I have a VFP application that is distributed to my users in .EXE form and has been running nicely for years. I have now incorporated some old code that was translated from Foxpro for Windows and still has some DEFINE WINDOW statements in it. At first I had problems getting a certain portion of the translated programs to work but I was able to solve it by putting a SCREEN=OFF in my config.fpw. That works fine when I run from within VFP, but if I put the SCREEN=OFF in my config file for the .exe, the application won't run at all. I can't find any explanation of exactly what the SCREEN=OFF does in the config file and why it works differently when I'm running an executable? Anybody got any ideas?
>
>Tobey

---

SCREEN=OFF sets the VFP screen off at runtime.
It can be used for building applications with top-level forms, and/or forms that reside in top-level forms.
That way the main screen with the vfp menu and so on are not visible at all.

I think you don't have any top-level forms.
Then all the forms of your app appear in the main vfp window, but that isn't visible so you don't see your app.
If you look in the task manager you can see if it is running.

Another problem you can have is that you don't have a read events statement in your application.
Then the application will start up, but immediatly shutdown again.
Always put a read events statement in your startup code at the end of the initialiation.