This same behavior occurs for Class Libraries. The ClassLoc field in a SCX or VCX can contain either relative or absolute paths. In either case, if the file is not found, the PATH is searched. This is quite hepful in case you ever move a class library that you've referenced into a folder in your path; otherwise, anything form/class referencing the original would be wiped out.

BTW, the documentation for FILE() reads:

If you do not include a path with the file name, Visual FoxPro searches in the default directory for the file. If it cannot find the file in the default directory, Visual FoxPro searches along the Visual FoxPro path, which is established with SET PATH.

However, it appears that searching the default directory and then the path occurs whether or not there is a path in the file name.


>This is 'funny' :
>
>If I type MODIFY COMMAND F:\EFFE in the command window, it will open EFFE.PRG if it exists in F:\. However, if it doesn't exist there, but if there is an EFFE.PRG along the PATH, it will open that one. It shouldn't. It's a bug or at least an unwanted feature.