>>>The config.fpw in APP will be ignored. The config.fpw will be only used by whatever launches APP. How do you run your app?
>>
>>I try 2 ways:
>>1. Start VFP normally then DO xxx.app
>>2. Double-click the xxx.app in explorer
>
>It's the same. VFP launches first and then your APP is run
>
>>Both seems to not using the internal config.fpw
>
>The config.fpw is processed only once. In your case VFP is looking for it and process it if it finds it at the time when it's launched. It wouldn't know or care about config.fpw in the APP it launches.
>Why don't you create EXE instead?

That APP is a utility that I use inside VFP IDE to aid my coding, it modify the IDE behaviours and adds items to VFP desktop, so I think make it app should be a proper choice..

In fact, I just pick it to test out how VFP uses fpw files in details. (e.g. what if I have my FoxProWCfg set, but incorrectly point to a fpw file that is not exist, will VFP continue to look for a config.fpw and so on ...)