True, Sergey, in fact the client I'm talking about is not upgraded to VFP8 <s>. ALl the advice I gave will work in VFP7 and above <s>.

However, ALLOWEXTERNAL does not work well for me IAC.

As I understand it, *both* are read in this case. I only want *one* read, even only set of values will "take". I also want the values to be available and editable.

Here's why: we use the CONFIG file to specify a whole bunch of other app-specific config values, and we read it as needed (like an INI file) on demand during the course of the app. The app only has to check SYS(2019) for this, very convenient.

But it's more than just convenience. These values need to be externally accessible and tuned as well. For example, work files location for our application (which is not necessarily based on TMPFILES but is temp space defined differently for TS users than non-TS users).

Now, here's why these settings are in the CONFIG file <s>: The network administrators know they can edit this file on demand (again, much like an INI file). They don't know the difference between TMPFILES and one of our settings, and they don't much care that one belongs to us and one belongs to Fox. In fact, they don't much care about *anything* Fox <s>. They just know they are allowed to edit this file as they move apps and disk capacity around.

If I had an app that was being invoked sometimes as a COM object and other times as a standard exectuable, however, I'd probably put some in the bound-in CONFIG.FPW in VFP8. But these would not be network-admin-type values.

See?

FWIW, all this stuff is pretty critical to think through when you deploy an app on TS plus "normal" users, otherwise it's sort of overkill.

>L<