Marc:

I agree with you. I have a BaseApp directory where I keep all my base classes, menu, program, application directory tree, etc. Each new app gets this copied to its home development directory. I modify classes, etc., from there. I only modify the originals if I fell it would helpful for future apps.

The only way this would be a headache for prior apps is if I want to adopt some of the new stuff in revised releases of the apps. At that point I weigh the pros/cons [i.e., time constraints, etc] to see if I really want to do that.

May not be classic OOP, but it works well for me. I adopted this procedure right after I upgraded to VS 6 and got all kind of messages of VFP not being able to find classes, etc., because the directory structure was different between VS97 and VS 6. The procedure I use is independent of where VFP and other stuff is installed now and in the future.

>Afier,
>
>I think this depends of how sure you are of your framework. Me, being cautious, I use a copy of my framework in each new application.
>
>It gives me the ability to extend the functionality of the framework without having to think of previous applications.
>
>On the other hand, I might very be creating a real version maintenance headache for myself :).
>
>My 2 BEF.
>