>
O-O encapsulation though says you shouldn't deal with the internal objects of the container. You can define a property at the container level and set it, then the container class would have code that would deal with setting up the textbox.
>

Not totally on point, but relevant nonetheless.

Which is why a control class is actually the better choice. Intrestingly enough, the control class - which has been around since 3.0 - is perhaps one of the most under-utilized classes in Fox. And yet....it is the one that is most like the one in VB and in .NET. The container class, IMO, is one of the reasons why Fox developers at times, has a difficult time grasping how composite classes work in other environments.