>>In addition to SCREEN = OFF; if you do not want FOXUSER files created, you can add a line to CONFIG.FPW that reads:
>>
>>RESOURCE = OFF
>
>How about the config.fpw itself? If there is no config.fpw on the user desktop, calling the application from the desktop icon will make the main VFP screen appear before my form, the same problem.
>How can I redirect my application to read the config.fpw at the application directory other than the desktop so that I don't have to put the config.fpw on the beautiful desktop of my user? Or other advice..
>

You have several options:

(1) Compile the CONFIG.FPW into the executable. You can include the CONFIG.FPW in the project under Other/Text Files or Other/Other Files, and it will be built into the executable and used automatically. i don't happen to like this option, since I use CONFIG.FPW to customize the executable to the workstation, but it's a common approach, and if you don't want to use CONFIG.FPW to override station-specific settings, it's the easiest approach.

(2) Change the Starts In directory in the shortcut. If no dirtectory is specified, Windows starts the executable in the context of the short directory, in your case the Desktop. If you specify a Starts In directory in the short, the app starts there. if no CONFIG.FPW is specified explicitly or built into the executable, VFP looks for one in the Starts In directory.

(3) Add a -C parameter to the command line starting the executable. You can specify the complete path and file name of a file to use for configuration by adding -ccomplete path of config file to the command line starting the application (no space between -c and the file name.) The file does not have to be named CONFIG.FPW this way, and can be anywhere on the system, but you must specify the fully-qualified path and filename.

(4) Use the FOXPROWCFG environment variable. You can specify the default location of a CONFIG file by setting an environment variable FOXPROWCFG to point to the file. If no CONFIG file is embedded or explcitly referenced by a -c parameter on the command line, the file specified in FOXPROWCFG is used.

This is discussed in detail in the on-line docs; look at Chapter 3 of the Installation Guide and Chapter 15 of the Programmer's Guide for details (both are in the on-line docs.)