Yes, I have to build this functionality into several different base classes and I agree 100% with you that it would be great to have a InteractiveChange() event in the container level.

---

>Yes, but you are building functionality into several different base classes to make a call to whatever is enabling/disabling these controls, right? To me, that's a PITA. That's why I wish we had an InteractiveChange(cObject,nChangeType) event at the container level: Anything there changed, we central source what needs to be done without all that redundant code in the controls.
>
>(Hey, Craig, send THIS idea to the Fox Team!) ;-)