>>5. Can anyone confirm with me that, if VFP9 is startup by double-click a scx or prg file, the "COMMAND=" line (if exist) in the FPW file will be run? My VFP9 is strange... I try to wipe everything in the VFP9.FPW as mentioned and only leave one line in it, that reads "COMMAND=MESSAGEBOX([I am run])"
>>Again, if I start VFP normally, I am prompted "I am run" but I I start VFP by double click a prg or scx file, there is NO "I am run"...
>
>It's more a matter of what's your .cfg file - the foxprowcfg environment variable is mentioned in just one place in help, and it doesn't seem to mean much, "Optimizing Visual FoxPro Startup Speed" only says "You can use the environment variable FOXPROWCFG to explicitly specify the location of Config.fpw. For details about the FOXPROWCFG variable, see Customizing the Visual FoxPro Environment.", but when you go there, it doesn't say a word about it. So maybe VFP doesn't use the variable anymore.
>
>IMO, I think your config.fpw is not read at all if VFP is run from a different directory (which it is if you doubleclick an .scx or .dbf). You can check sys(2019) in both cases.
>
>You may just be better off by calling your file config.fpw - that seems to work even if I open VFP via doubleclicking a file. Alternately, you may go to registry and edit the open command for such files to include the -c switch.

I did check sys(2019), I check sys(2019) after double-click a prg file in Win Explorer, let's say it is accurate in telling which fpw is being used, just like what I have mentioned in my last post, item 4), yes, the right fpw file is used.

In my case, the Windows file association "Open" action for prg or scx is

"F:\Coding\Vfp9\vfp9.exe" -SHELLOPEN "%1"

I seems, any file associated with VFP9.exe is passed to it as an argument with the SHELLOPEN switch. I strongly suspect that the -SHELLOPEN "%1" is internally converted to a COMMAND=MODIFY COMMAND %1 or something alike and that COMMAND= is treated as the last COMMAND= line in FPW file. So even if I put 1 COMMAND= line in my FPW file, it is ignored in the Win Explporer double-click case.

I eagerly want to know if I am the only one faces this situation... or it is a common to everyone.

Btw, if I replace the COMMAND= with _STARTUP= it works! even for the win explorer double-click case as discussed. However, that does not solve my problem because _STARTUP item starts too early, even before VFP has a chance to open up "Properties window" or other system windows that it suppose to open.

I know, I could simply create a intellisense shortcut and start everthing manually from command window, just type "au"+[enter] that 's it. I just don't belive I can't save that "au"+[enter] thing... :(