>>They should be. If you have a private datasession form and it instanciates a new form class that has the default datasession, it should be using the datasession of the first form, the private datasession. If that's not what you're seeing, you must have some code somewhere in your class hierarchy that's fooling around with the datasession setting.
>
>The one situation where this will not happen is if the parent form launches a child form with a goApp.DoForm('mychildform'). This child form that is set to use the default datasession will inherit the datasession in which the goApp object was instanciated [probaby the VFP DS -- DS #1].
>
>For the child form to inherit the parent DS, you have to DO FORM MYCHILDFORM directly from the parent form.

Ahh, how soon we forget the details. Good point Mark. An object done via CREATEOBJECT() inherits the datasession from the creating object, so if it's done from goApp, it's going to use goApp's datasession. You still can use CREATEOBJECT() (instead of DO FORM) as long as it's called directly from one of the form's objects or methods to inherit the form's datasession.