Dionísio,

I use a set of relative paths that work for all my projects. Typically my SET PATH on the Tools/Options/File Loations is:

..\; .\forms\; .\source\; .\classes\; .\menus\; .\reports\; \vfp8\tools\;

So it looks 1 level up for all my common code, then down to the places I store project code, then it finds my developer tools that I just put in the vfp tools folder.

>OK, Now I understand, but in any way it would be good if this functionality was increased.

There will be times that I may open multiple projects at a time and launching the designers from the project keep everything straight. I don't necessarily want to change to those other directories.

>I am using a project hook for automatically to set the default directory
>like this whenever I open a project the class project hook arrow _vfp.activeproject.home
>as Default Directory, but even so VFP doesn't consider the sub-directories to leave
>of Default Directory, putting under an obligation to type SET PATH TO...
>
>VFP would be easier for beginners like me, if everything was made automatically,
>after all a lot of thing happens starting from the moment that the user forgets to write
>SET DEFAULT and SET PATH, the two commands would not need like this to be written.
>
>Perhaps I increase more an item in Wish List, but with the amount of things
>that are for there...: -)

By all means make these sorts of feedback on the wishlist, they are always wanting to find the stumbling blocks that impede new users from making the tool productive. Welcome to VFP!