>Hi Mike,
>
>I had thought of that as well - because I know in VMP it tracks the calling form which makes it easy to switch to that datasession. I am not sure what the "right" way to do it is - somehow it seems "safer" to work in a new data session but then in reality, if it's tested, it really does not matter. The one thing I like is that if I am working in a new session and the user presses Cancel, there is not much to do other than to signal the calling form that nothing is happening. But again, this can all be done when sharing a datasession. So more a case of style than substance.

Until you try it with thousands of records.

I take this technique farther. I guarantee I use the same alias for a cursor across different forms. So, if I have a cursor full of customers, when the child form launches I can expect that customers is filled and not re-query anything. Less is really more.

>
>Albert
>
>>>Could do that. I kinda like forms to be as "atomic" as possible (if that is the correct computer term) so that everything is contained in them without affecting any other form. But it is an option. Thanks.
>>>
>>>>What about using the same data-session and same view for both screens?
>>
>>Hi Albert
>>
>>I have my forms determine if they're called from another form and if so, switch to default data session, or if you want to be really specific, the data session id of the calling form. This is done in the either in the load or in the dataenvironment beforeopentable.
>>
>>There is no shoveling of data around.