>>DO setup
>>
>
>The framework is set up such that it will run without being built into an .app or .exe that is why the path is defined in that command.
>
>However, the devlopment path (set path to) should contain all necessary Framework and application level directories so I can see that
>
>DO setup
>
>would work. I made a small change so I could also add my own paths to the development path, but Kevin did not implement it or anything simmilar up to this point.
>
>>Since setup was bound into the project I did not see any reason for a path. I am sure you have a good reason to do this this way.
>>
>
>When you type DO MAIN the project is irrelevent to FoxPro finding procedures and classlibs until you BUILD that project and run the program as an .APP or .EXE which FoxPro will search first to find libs and progs.
>
>BOb


Actually I figured all of that out late Friday night. For 7 years I have programmed via an EXE (Code, compile to EXE, test). My project organization had too many directories to keep all that I needed in a path, just would not fit. Plus I have always used my own frame work so to speak. I have purchased lots of Fox add-ons but never a complete framework that I had to figure out and work within. Kind of disorienting at first. I worked real hard all weekend and made a lot of progress on becoming oriented within MM. I am sure I will have many more questions but I feel very good about this week and working within MM.

Thanks for your help.