>>p.s. "naming convention" is when we all gather in a hotel, drink and invent names.
>
>Hi Dragan,
>
>That sounds like a sensible choice, however the disk file has been there long before our current app was developed. The disk file is named config.fpw, hence the conflict with the config.fpw included in the project. If I had a choice I would have renamed the file in the project, though I don't think you can make the exe read an internal config file other than config.fpw. Perhaps I should try...

I failed to notice that this was about config.fpw, which really is a special case. Like Sergey said, you can't rename the internal (or VFP wouldn't know that it needs to read it as a config file - it knows it by this special name); you can rename the external except in your case it seems to be an external limitation imposed on you so you maybe can't do it.

VFP will read both, and the outside one is the secondary... and overrides the internal, IIRC. Haven't played with external ones much for runtime, though, simply because anyone can edit them and you never know when you may find a power user who knows enough Fox to be dangerous. I prefer to maintain settings in code, or in an internal config.fpw.

There were a few messages in this thread about internal vs external config file, so you may be better off following that line. What I said may work for other cases, but not this special one.