>I have considered this in the past but the problems inherent with subclassing the entire Framework (check out the Developer's Guide for details) have made me reluctant to provide this layer since, no matter how you slice it, you end up breaking the inheritance chain on one side or the other.
>


Actaully, if you look at the way it is done in the new release of codebook by Flash you will see that the inheritence is maintained and the developer is given a place to modify the framework without needing to subclass as much, and loose inheritence.

An example would be.

cBaseForm
--- iBaseForm
------cBizObjForm
--------iBizObjForm

So, iBaseForm is a subclass of cBaseForm, then cBizObjForm is a subclass of iBaseForm... This allows the developer to modify iBaseForm and still inheriet any changes made to the framework in cBaseForm.

Also, and changes made in iBaseForm are inherited by cBizObjForm. This to me seems to allow for simpler modifications with less subclassing.

If you want the specific problem we have I will outline it... but the above type senerio which adds a developer controlled level for each class would help us alot.

BOb