>>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"
>>

>
>Same as "F:\Program Files\VFP9\vfp9.exe" -SHELLOPEN "%1" in my HKEY_CLASSES_ROOT\Visual.FoxPro.Table\shell\open\command registry entry. And the same thing here - if I open my VFP by doubleclicking an associated file, my command doesn't run.
>
>>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.
>
>Doesn't work for me if I just put it in the config, but if I set it in menu\tools\options\file locations\startup program (and click Set As Default), it ends up in HKEY_CURRENT_USER\Software\Microsoft\VisualFoxPro\9.0\Options in the _startup key there. In my case, the code I'm running isn't doing much - changes VFP's icon, adds a few things to system menu, sets the path and launches DO (_taskpane).
>
>
>>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... :(
>
>I also tried with _shell=mycode.prg ... maybe that'd work in your case. The moment it tries to open the command window, it'd do (_shell). It didn't work when set from config.fpw, but may work when set in code.

I think the best choice is to tweak again my startup prg and make it a _Startup item in FPW.

Anyway, thanks for trying to help.