>OK, I'm running into a couple of issues with paths. The first is that I've tried setting my path: SET PATH TO "C:\projectname,C:\projectname\data,C:\projectname\forms,C:\proj..." in numerous places such as in the code that I set as main, in options from the designer window, and in form inits.
>
>Regardless, when something is called from the C:\projectname\reports folder (or forms, menus,...) the program can't find it.
>
>The second issue is that this program is intended for multiuser use, and I can't visualize how these paths are going to be manipulated when installed. IOW, what if they are installed on drive D:? I've already hardcoded the paths to be drive C:\whatever.
>
>I've started researching these issues in the msdn online help, but would appreciate a professional's point of view.
>
>Rodney

Hi Rodney

The simplest rule, as others have said, is to rely on the pathing set in the config.fpw (or whatever alternative config you run in development.
As long as your production config.fpw is correct, VFP will find the files.

Apart from databases and tables, the files will be in the executable and pathing is not a worry. Nevertheless, there are some traps with databases and tables. VFP stores the path of the databases in the data environment, and if that path exists, it uses it. You might want to run on a different set of data, and it is frustrating to find that you are still looking at your original data set. The only quick way out of this is to rename the directory with the original data set (restore it later). VFP then searches and finds the datbl;es and databases as long as they are on the external path.

HTH