Ken,

I'm with Jim on this one. Ideally, you don't want any form object interfering with any other intentionally and this almost requires a private datasession. What he is referring to for child forms is that a child modal form launched from a parent form with a private datasession uses the default datasession because, in doing so, it inherits the parent form's datasession: very useful behavior for data drill-downs or picklists or other stuff.


>In my opinion private data sessions are what should be used most of the time. The only exception is for very specific situations where a child fomr needs to access the data of its parent.
>
>A private data session sets up a situation where one form cannot interfere with the data environment of any other form. Prior to private data sessions we wrote alot of state saving and restoring code to allow multiple forms to be visible at the same time. With private data sessions none of that code is needed because VFP handles it for us.