>>>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..
>>
>>Sounds like you have the application sitting on the desktop. Why not put the application (and the CONFIG.FPW) in it's own directory and create a shortcut to the application instead?
>
>My question may not be clear enough. I have an executable to distribute to users, with help of setup wizard. After installing the program into the user's machine, I create a shortcut icon on the desktop (to link to the program directory). The problem comes when I run the program from the icon, the VFP screen appears. This is because there is no controlling config.fpw on the desktop.

Ah. I think you'll need to modify the shortcut so that the 'Cmd Line' field contains not only the path to your executable, but also -c{PathToConfig.fpw}\CONFIG.FPW