This was one of the things that really got me too, some parts of foxpro ignore the full path you give it to a prg if it can find it in one of it's seach paths anyway, which seems really stupid to e, but I hear it's been like it for a while and is not likely to change.

it seems that if you still have any reference to your old directoies then it will make them a part of the search path and this set of search paths is effective when running the program too. I found I had to have a

set path to

at the beggining of my program to ensure weird things didn't happen.

sorry I don't really have a solution apart from go through the code and check every mention of a path.


>I maintain and expand an application which is based (loosely now) on the CodeBook and Visual FoxExpress 5 frameworks.
>
>We have shifted our development directory structure around considerably in order to work better with SVN version management. As a result I need to understand how the framework sets up values for PATH, CLASSLIB, and PROCEDURE.
>
>This is what is confusing me. Even when the application is run in a network directory which bears no resemblence to the development tree structure, these settings still append the (nonexistent) development directories to the references to PRG and VCX files.
>
>This seems crazy to me.
>
>1) Why doesn't the BUILD process by itself insure that all components can be found at run-time?
>
>2) If one must have voluminous lists of components in CLASSLIB and PROCEDURE, how does it help to refer to nonexistent directories?
>
>Scratching my head. :^}
>
>Peter