>>FWIW, I have never had this problem, because my framework doesn't use a DoForm method. Rather, all of my forms register themselves with the forms manager when they are started. This keeps me out of the parameter passing mess, lets me use DO FORM whenever I want, and avoids trouble like you are having here.
>
>How are you doing that. FormManager.AddMe(this) code in the form's Load event? I'm currently doing it the other way and need to change so I can take advantage of the default datasession.

IF TYPE("oForms.Name") = "C"
	oForms.Register(THIS)
ENDIF

Then similar ode in the form's destroy event that unloads it.

I really like this a lot better, because of the cleaner parameter passing, and complete backwards compatibility with all code previously written that uses DO FORM. Also, just seems like better encapsulation.

Bob mentioned that a DoForm method is nice when you use vcx based forms, which I guess is true, but I don't use them at all, so this is not an issue for me.