>>Even better... (and more OOPish) than Michael's suggestion create an Assign procedure on the container's Enabled property that does the SetAll. This is better because the Refresh gets call alot and this way the code runs only when you actually change the value.
>
>Hi Craig,
>
>I'm curious, and open to learning new tricks. And since the original poster has not asked, I will. How exactly do you do this? I don't know of a way to add a new method to a control. Or do you mean a form method that gets called when you want? To be honest, I usually let each control take care of them selves. But I thought he didn't want to do that. So, if you have the time, I'm willing to learn this.
>
>TIA
>Mike


You should never use the control "as is", but should subclass it. You can then add whatever methods you want. If you want to add an Assign method, call it Enabled_Assign.