>Mark,
>
>This isn't really an answer, but I find that the Formset class is really pretty useless. Maybe that's overstating it, but the point is that I find that it's generally more trouble than it's worth. What I prefer to do is to use custom properties to hold on to object references to logical child objects, so that I don't have to live with the more restrictive model that formsets provide. Just thought I'd stir up some trouble while I'm killing some time.
>
>Mike
>
>>Didn't some clever person devise a method to stuff several forms (individual SCX's) into a single formset SCX? I have some situations where I would prefer to use this utililty rather than saving my forms as classes and dumping them into a formset. In general, I've found this method to be cumbersome because most of these forms are of the "use once" variety, and I consequently find myself needing to frequently modify the base class. This is a nuisance because you cannot edit the base form and the formset at the same time (i.e., Cannot modify a class that is in use). So I would prefer to use a forms-to-formset builder utility thingy. How about it?
>>Thanks!

I want to reply here just because I extensively use formsets. They are not useless at all and provide flexible implementation of class model. Formset allows to add/remove forms on-fly from classes, i.e. I use it as container only to store some generic methods (start froms, handle toolbars, etc). All form specific methods store in corresponding VCXs, and edited using Class designer.