You can change most of the VFP setting in your app w/o config.fpw. The ones that cannot be changed have to be specified in config.fpw for VFP startup.

>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 ...)