>
>I'd really like to hear about the scenario you have in mind...
>
>Regards,

Basically it has to do with controls.

We like the ideas of the control container, and think this should be the place where we encapsulate some code that looks to the data dictionary (most likley via SDT) to populate some values like lMustKey and lMustValidate. (and maybe even the label, default value, inputmask, etc.)

Also, we think that that control is the place to put some common validation code that will call our validation object.

Anyway... if we subclass the controls in kcusctrls we would have to put this code in every control. The other choice is to rebuild all of the contiand controls... by subclassing ccontrolcontainer and then rebuilding all the contained controls that you have already built. This would require a lot of cut and paste, and if you changed the code in those controls, we would have to retro fit the new versions that we built in acontrolcontainer.

However, if there was an icontrolcontainer which you used to build the contained controls, then we could modify the icontrolcontainer and not loose any functionality of what is in ccontrolcontainer, and not have to cut and paste what is in each contained control that already exists.

Perhaps I am missing something obvious, or not so obvious?

BOb