Gino,

That seems like one way to go, but it also seems to throw out the main advantage of OOP.

OOP's big selling point, as far as I can discern, is REUSEABILITY. Yes, there is a "price" to pay for this "feature", and an important one is to be sure that CHANGES ARE FULLY AND WIDELY *TESTED* BEFORE INTEGRATION INTO (personal) BASE CLASSES!
If you are going to 'keep different versions of your framework around' (each revision becomes a new version) you will also inherit all of the OLD PROBLEMS inherent in PRE-OOP. You just are absolutely no further ahead!

By the way, Paul R's scheme of 'starting from scratch when the customer wants final ownership' (rather than use his framework) also feels somewhat at odds with both OOP *and* productivity. He is surely subject to legitimate underbids by competitors who do *not* employ this scheme.
I rather view any investment in a framework as my competitive *ADVANTAGE* - I can do the work more RELIABLY and IN LESS TIME regardless of who fianlly "owns" thae system in question.

Just my 2¢ worth.

Jim N

>Here's the answer I derived from all of your input:
> I am going to use a seperate copy of my framework for my next application, being sure to keep application specific mods, and generically useful mods seperate. After that, I will use that as my framework... It really comes down to a question of how satisfied you are with the fundamental structure and flexibility of your framework. It seems that once a framework is decided on, it will take some will power to avoid making changes to the structure of things. After all, you can always change frameworks on your next app!
>
>Thanks for all your input
>-Gino