>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,

Avoid hardcoding the path, especially with a drive letter. What I typically do is create a path statement that contains the paths to the sub folders *relative* to the folder of the main PRG or EXE.

Example, if I have a project hierarchy as you explain above, and assuming the EXE gets built in the main "projectname" folder, my path statement would be:

SET PATH TO .\DATA, .\FORMS, .\LIBS, .\PRGS, ...etc..

So long as you distribute any files required (including the folder hierarchy) by the EXE but not included in the EXE, it should work fine.

HTH,