>The location of the EXE may be a different matter to you, but it is somewhat critical to answering the original question, which is about SET PATH <s>.

Um, yes... didn't read the specs recently, probably says something about the original question, but who reads the specs :).

>We are talking about how VFP components will be found. Regardless of the current directory, in most people's deployment, application components are going to be installed in several well-defined places. One of those well-defined places is definitely "in a position relative to the EXE" (IOW, [INSTALLDIR], speaking in InstallShield terms).

And the position relative to exe may not have anything to do with current directory. The executable may reside in one directory (and find its components in the virtual directories inside the exe and along the DOS aka Windows path, system directories etc) and yet execute in another. Most of the time, this is not the case, but we often have loaders which load a local exe to run on server, or have multiple shortcuts for the same exe to run on different sets of data, each in its own set of directories. I know there are better ways to achieve the latter - but for those guys who do it that way this is probably a problem they solved long ago.

p.s. I don't think the original question was that original... I've heard it before :).