>Hi Bob,
>
>Assuming an object named oPreferences, then in the INIT() of the textbox class you cold do something like this:
>
>oPreferences.Execute( THIS)
>
>In other words, before visibility, have objects feed themselves to a machine that abstracts the process of, among other things, setting user preferences.

Steven
How about that ... you've found another one of my blind spots. When I use init() in a form, it seems natural; using init() in a control on a form is less common for me, but still pretty obvious when it is needed; but using the init() in a control's base class somehow never occured to me.

oPreferences can pick up the the user's preferences from a table when it's first instantiated, pass it along to controls when requested by their init()'s and update the preference table when the user changes his mind.

Thanks
Bob