Hi Victor

By this do you mean your mid level class sits between your framework and your application subclasses.

If so then surely changes you make to the mid-level classes end up reflecting in all your applications along with all the testing and documentation changes this entails.

It sounds powerful and safer then doing it all from your framework classes but I would always be scared of the documentation/testing overhead of any changes I made.

By this I mean testing each app efected by the change (can't see any way round this one) and also documenting each app effected.

Of course documentation for each class does not need to be reflected in all the apps. You just tell them to look in the documentation for the mid-level class. Sounds like a good reason so do all documenting in HTML with Hyperlinks. nice:)

What are your feelings on the testing side of things though?



>What I do is keep all my framework files in one location on my machine. All my projects uses this. Any changes that need to be made to this...I subclass it all..never even touch the framework files. Eventually I found a need to create a 'mid-level' class that I also reuse a lot.
>
>>In his (very good) book "Advanced OOP for VFP" Marcus Egger preaches that the best reuse of classes would be to share them over all your applications. We find this a nice idea but practically impossible to execute because you would influence all your projects by each change of a class (also those apps you do not want to touch anymore). We ourselves copy our framework with all subdirectories, classes and files into a new separate directory at the start of each new project.
>>Is there anybody who has some more ideas on this ?