>Sorry to pick your brain again, but you said you put it in the config.fpw. So you allow the users to change this config file?

Sometimes it's very advantageous to allow them to do so. I had an experince like that today. If you're not going to allow changes, then simply build in the config file. You'll have to make certain, however, that any local directory referenced therein exists, but beyond that it's cake.

>I don't feel comfortable hard coding the temp to always be say C:\TEMP, their C: drive might be the smallest drive and not have the room available. We have our config.fpw compiled into the exe. Is this not a good idea? I thought that would make sure the application was using the right config file.

What I do (and I'm a corporate developer so I can set some standards) is not allow them to modify the target directory of the applicaation. I run a post-setup executable that actually does the real work of installing the executable. The program that actually does the installation asks the user if they want a desktop icon, creates the configuration file, etc. In regards to the configuration file, my VFP apps don't have a config.fpw file. The primary portion of the filename is the same as the executable. I create and modify the shortcut so that it points to the proper configuration file for each exe.

hth,