>>Thanks to Gary and everyone who contributed ideas. It seems Gary had a VERY
>>valid point. I considered everyone's great ideas, but I especially like the idea
>>of using AddObject in the Init method to add the object after everything else has
>>Initialized.
>
>Gino,
>
>The only weakness with Gary's idea, which will work perfectly, is that you loose the ability to work with this object visually within the form since it does not appear in the form designer.

Exactly. In this particular situation, I was dealing with a non-visual "component" type class, which can be dropped onto the form. It handles all the geometry (resizing, etc) of the objects on the form based on their cGeometry properties (if they have one...) So for class-based forms, it seems reasonable to just used AddObject. In other cases where I had visual objects, I would place the code in each control's Init method or in the Init method of the form (depending on whether or not Init of one control depended on properties of another)