Well...you know how dim the light can be sometimes (not that that would happen to you), its the old brain fart trick.

Anyway, yep it works great. Now my boss won't have to remember how I built my directory structure for the project. The "set path to" includes the relative path to the common classes and prog's also.
Thanks for the help

>So you have the project hooked properly and you should now be compiling. Doesn't your pathing switch work now?
>
>>Thanks Mike
>>It hurt a little...but I thought the hook class had to be in the project to run when it was opened. I could not find access to the project properties (using vfp6). I thought that was what the checkbox was for.
>>
>>Well, I guess I need your details cause I really need a solution.
>>
>>
>>>Hi Chuck
>>>
>>>Not to sound like the quack doctor, but if it hurts <g>...
>>>
>>>I have a project hook and don't see this problem. It seems your project class is in the project. Take it out. IMO, the only things that should be compiled into the exe are things that make the client's project work. The project hook is for you, not the client.
>>>
>>>I take a different approach to pathing, but I have considered something like your approach. If you're still having troubles, I'll fill you in on those details.
>>>
>>>Mike
>>>
>>>>I created a projecthook that does "set default to" and "set path to" in the init. In the destroy I reset it development root directory. This works just fine. Problem is I cannot compile the project with out getting an error that "the project class is in use and cannot be recompiled". Of course that means I get an imcomplete compile and my exe is not updated with changes made. This "feature" is annoying. I need to be able to set the default directory and path to its sub-directories when the project is opened so I donot have to do it manually every time. Other developers complain about have to set the default paths. Anyone have an idea on how to release the projecthook class for compiling.
>>>>
>>>>Thanks, Chuck