Hi Sergey,

Thank you for your help.

I'm using VFP 7.0 and 8.0. Thats why this placed in the "general" category. ::)

It works fine now with VFP 8.0. It is not my initial expectation that the internal fpw will be replaced as for an external config.fpw, but the implemented way to read the external after the internal will do.

For that it is to note that
D:\mypath\myexe.exe -C
will not end up with the internal file not loaded. This needs the -A switch.

It's no big deal for VFP 7.0 I will not hand out new versions on that.

Agnes
>Hi Agnes,
>
>What VFP version are you using? In VFP8 adding ALLOWEXTERNAL=ON to the included config.fpw will allow to use external config.fpw. In previous versions external config.fpw file will be ignored regardless how you specify it if there's included config.fpw .
>
>
>
>>Hi All,
>>
>>I've a problem in understanding. I include a config.fpw to my application. This one works fine.
>>
>>Now I try to use a external config.fpw using the -C switch like
>>

>>Run /N c:\MyPtah\MyExe -Cc:\MyPtah\external.fpw
>>*or to use no config.fpw like
>>Run /N c:\MyPtah\MyExe -C
>>*or
>>Run /N c:\MyPtah\MyExe -A
>>

>>
>>whatever I do it uses the included config.fpw.
>>
>>according to help
>>Settings in a Config.fpw file that are bound inside an application can be overridden by specifying an external Config.fpw file, using the -C command-line switch when starting an application or Visual FoxPro.
>>this should not work this way.
>>
>>What do I wrong?
>>
>>TIA
>>
>>Agnes