>If my path can be of any help then, let me tell you this: Pragmatism when it comes to OOP is _the_ key. I do not believe that you can model a framework in advance. I couldn't in any case. You refine it with every application, because you tested it. Contrary to what we are (were?) used, if you framework does not work right, and you do not know that in advance, you are in trouble, because you cannot change parents. Well technically you can of course, but practically you cannot if you do not want to end up like that dog trying to catch it's own tail.
>
>Bad objects is the worst that can happen to you. And the only good objects I know are objects that work in production.
>
>Do not tell me I did not warn you. :)
>
>Marc

I hate to complicate this discussion any further, but considering the framevork to be an important and big part of an app, I'd have to say that at some point, framework will cease to be general and go into things speciffic for each app, without meaning we have to begin hard coding. IOW, parts of framework probably should stay at one place and be general, but it's finding that fine line where framework gets too oriented towards a speciffic app that's tricky. I mean, some changes on framework can work beautifully at a low level, affecting all apps involved, others might cause a disasters we all fear.

Having said all that, I still suspect Visual Source Safe to be the best solution, something my boss is still contemplating, I'm afraid, therefore I can't say much about it, except that other's comments are all but negative.

Best regards