>>>Check the command line [for] a "-c" option [...] Also, if they have a FOXPROCFG (sp?) environment variable
>>
>>Thanks! It works! However I am just wondering why it works for some users without the -c switch in the command line!
>
>My guess is that where it *wasn't* working they had a FOXPROCFG environment variable pointing to a different config.fp. You shouldn't have to put the -c switch in the command line if the config.fp file is in the same directory as the exe, unless there's some other thing overriding where FoxPro looks for the config.fp.
>
>In other words, if it were me troubleshooting this, I'd have looked for what to *remove* from the non-working computers (probably the environment var), rather than *adding* the -c to point the exe back to its default.
>
>But (a) I wasn't troubleshooting this, (b) your solution works, (c) as usual in FoxPro, there are a number of ways to approach the problem. I'm telling you your working solution is wrong!

Thanks for your prompt replies. I guess I didn't think that the set foxprocfg line I had put into some users autoexec file was affecting anything because I had the memvar count up over 1000 in that config.fp file and they were still getting too many memory variables errors. I knew that config file wasn't being used because when I did a display memory from those workstations the memvar count was at the default, not at the count set in the config file. So somehow the default was still overriding the config pointed to in the autoexec file. So now I have all the workstations using the config file I want - without using the -C switch.

Rhea Urusky