Hmm. That's interesting. My FormManager retrieves size/position info for each form (including child forms) and stores it localy in a table. That all gets handled in from the oForm.DoForm and oForm.ReleaseForm methods.

Would the Parent form call oForm to retrieve that information for it's child form?

I liked Erik's idea because I can get rid of the DO FORM wrapper. Seems like it simplifies that process a bit (for the times when I forget to use the wrapper *s*)

>You don't need to change anything about your form manager to make use of the data session behavior.
>
>What you do need to do is to catagorize your design specifications.
>
>My specs for the form manager say that it is responsible for creating and managing independent forms. Dependent forms are created and managed by the object that they are dependent on, in the case of a child form it is created directly by the form that needs it and managed by that form.
>
>For example when it comes to application shutdown, the Form manager will attempt to close all of the forms it created. Any form that has created a child form will attempt to close that child form before it allows itself to be closed.
>
>Every form (based in the base form class) keeps a reference to its creator and also a form that launches a child form keeps a reference to its child form.