>>oRox, the real answer is inheritance! If you had your forms derived from the base form class, and you fixed it in the base form, it fixes it all over the place...
>
>< smirk > Well DUH Steadman. But I figured if the person posted a generic question such as this, chances were inheritance didnt apply & the forms were either SCX's or separate classes not related.
>

Yeah, but at least give'em a chance to get it RIGHT next time. And you can apply inheritance at any level from the base up!

>And SetAll() can be very useful for making a sweep up things in a Form or other container. For example applying global touchy-feely user preferences that warp the general UI appearance. Who in their right mind wants to inherit that overhead... or worse yet have multiple form classes for the same form that all appear differently. Situations like that, SetAll() is a godsend. In fact if I sniff a potential for sweeping property settings, I slap stuff in a container right off the bat. Perhaps this practice just feels good since I use a commercial framework with extensive inter-operability amongst common object interfaces.

Where's the SHAMELESS COMMERCIAL ENDORSEMENT warning, along with the big bonus check for telling what you're using...