>>That's primarily the reason for new Session object. We found lots of folks using Form objects for their COM servers just to get a private data session, and as you know, Forms consume a lot more memory.
>>
>>Randy
>>
>>>Thanx, if found it...
>>>
>>>I see how it can be useful in setting up datasessions in the new multithreaded COM objects.
>>>
>>>Charlie
>
>The new Session object is terrific for creating a lightweight private data session. Trouble is, it seems to only create private data sessions even when you want a default data session. Is this by design?
>
>
>lo = NewObject('mysession')
>? lo.DataSession && this returns 2!!
>
>DEFINE CLASS mysession AS SESSION
>
> datasession = 1
>
>ENDDEFINE
>
>
>Thanks
Hi Paul,
This is either a bug or an error in documentation. The docs say that you can set it to the default datasession, but when you create the object, it's always private.
George
Ubi caritas et amor, deus ibi est