>I have a config.fp file in the same directory as the exe (foxpro 2.0 Dos) on our file server. We use Novell Netware. I use the config.fp file to increase the memvar count as the default of 256 is not enough anymore. I have discovered that only some of our users computers are using the config file, the rest are not 'finding it' and so are using the default for memvar count. I have printed the 'display memory' from each workstation to determine which ones use the config file and which ones don't. I have no idea why some pick it up and some don't! Any ideas?? I have checked the version of Windows each pc runs but some of those that use the config file have the same version as some of those that don't. I would greatly appreciate any info as to what it might be that makes the difference as to whether the config file is used or not. Thanks.
>
>Rhea Urusky

Check the command line definition on the computers which "don't see" the config.fp, does the command line include a "-c" option pointing to a different config.fp? The command line option takes precedence over FoxPro's default sequence of "what directories to look in for config (etc) files". Also, if they have a FOXPROCFG (sp?) environment variable, that takes precedence over Fox's default search path. (Command Line option takes precedence over environment variable.)

Depending on what version of Windows each computer is running, you may be looking at a File Manager icon, a PIF file, a Desktop Shortcut or a Taskbar (Start Menu) shortcut. (Or all of the above if your installed base is really varied ... poor you ... :)

HTH