>>>Why Not? It is easier to mange two forms one set of source code for two forms to talk to one another.
>>
>>What do you mean?
>>
>
>I have a couple of forms that call certain routines that would be useful for both forms. Such a show_labels routine which display information on both screen simultaneously. I understand that i can call the routine by using the form name of what is was instanciated as. Although this would seems easier in the formset to just call the routine THIS.PARENT.PARENT.ROUTINE.
>
>
>>>No guessing at what form calls another..
>>
>>I don't guess what my forms call each other: if my forms have a speaking relationship, they do it through a forms manager or through a direct object reference that was assigned when on of the forms was instanciated.
>
>
>Would a formset be the same as a form manager?

Not really. A formset is a set of interrelated forms, usually sharing a data session. A form manager is an object that tracks and manages the form instances currently active at any given moment; it tracks each form, may hold certain state information about the form instance, and provides a unique object reference for the form which can be queried at any time. The form manager object deals with the form set as a whole; it provides a common point form form instantiation, and also provides an object with methofs that aplly to the collection of form instances as a whole. In many cases, it handles issue such as dispatching forms when one form is released; in my application, it's responsible for such things as enforcing single-instance forms, so that if the user tries to instance a single-instance form that is already active, the new instance is not started and the existing instance is activated. My form instance is also intimately connected to my aplication object; when the application object detects a shutdown request, it notifies the form manager object to attempt to either complete or revert any action in progress.

>
>Shawn