To follow-on John's point, you could allow for this even in a private datasession. Just make sure you pass as a parameter to the child form, the datasessionid of the parent. Then, in the load event of the child, overwrite the value for the datasessionid. Even though a second private data session will be created, it doesn't have to be used...

I have had to use this approach on a configuration system for our office.

>If the child form references data from the parent, it can be directly reference in controlsources without having to reopen anything if the datasession in the child form is set to Default (NOT Private).
>
>You won't get the lookup when selecting a controlsource from the Props sheet, but you can type in cursor.field and it'll work fine.
>
>
>>
>>Scenario>
>>
>>I have created a form with combos that searches an office. On this form is a cmd button that fires a form with a grid. When a user selects their choices in the search form and presses the GO cmd button, the form fires and displays all the information that about the OFFICE the user selected (in the grid).
>>
>>
>>Concern:
>>I do not want to have a grid pop up on a form (which is fueled by a pview) when the user hits the GO cmd button, to see all information pertaining to their selection.
>>
>>I want to have my OFFICES FORM pop up with the "office" the user selcted -- as the current record.
>>
>>QUESTION: Can I simply copy my OFFICES FORM and place the pview that works the grid, into the control source of the OFFICES FORM? Then, in theory, I could call my OFFICES FORM from my search form, and the office the user selected in the search form would be displayed.
>>
>>Is this a viable solution, or should I approach it from another angle (meaning, this is crazy!!!)?
>>
>>Just curious!
>>
>>Thanks for any input
>>
>>Jason