I understand now, looks like a workable solution.
>Hi Bob
>
>>How is what your doing different than just setting to a default datasession?
>
>I've added rules to my form class. If the form is called from the menu it uses a private data session. If it is called from another form as either a picklist form or a child form, it should adopt the calling form's data session id. That's how it is "dynamic" IMO.
>
>>
>>The issues I referenced are when you try to work in several datasessions within a form. and most of those issues are tied to things that are scoped to datasessions.
>
>Those are all manageable. The warnings over the years seem to suggest just changing datasession is problematic.
>
>>
>>Bob
>>
>>>>Hi all,
>>>>I was wondering if it is possible to change the datasession in a form from default to private
>>>>depending on where it was called from?
>>>>Thanks.
>>>
>>>I've been doing dynamic data session forms for many years now. There have been none of the widely (almost mythical) reported unexpected results, but that may be due to how I'm doing it. Without all the conditionals, subclasses and error handling, I'm basically doing this in my form class Load so the datasession is already setup for opening cursors.
>>>
>>>
LOCAL loCallingForm
>>>loCallingForm = _Screen.ActiveForm
>>>SET DATASESSIONID TO m.loCallingForm.DataSessionID
'If the people lead, the leaders will follow'
'War does not determine who is RIGHT, just who is LEFT'