>>Nadya if you are using tables on an network then all the tempory tables will be on the network in this case you can have performance issuesin this case why don't you allways create a folder on the c drive an point to it on the config.fpw
>
>Hi Alexandre,
>
>Usually, we store our temp files on the local drives. For instance, I configured my VFP to use d:\TEMP, because my D drive is 20GB and C only 2GB. However, most of the users don't have big local drives, but they may need to run DataDict application, which changes tables structure for our huge tables. So, my manager suggested to create Work directory for this particular application on the Network drive, so it would be always enough space [Here, BTW, another problem, since this drive is 68MB and DISKSPACE() or George's workaround don't return correct space information, we discussed this problem couple of months ago]. I created config.fpw and placed it into my application directory, but it doesn't seem to make any effect...
>
Nadya config.fpw is only load when you start vfp or an .exe you said that your users have vfp installed and are running an .app files so the config.fpw to be loaded must exist on the start directory or on a directory on the path as I said vfp first looke inside of the exe for it then on the current directory and at last on the path if he finds any then vfp will load that config.fpw if not then uses the default's values.