>>>Alternative might be to save result in an ADO stream for example or recordset which you would be able to access from any session and get as a cursor idf you need using CA.
>>>ADO is a simple alternative and there others like XML, array ...
>>
>>...and a simple scatter name, then returning the object to the caller. Fields are now properties of that object, and the caller can do anything with them.
>
>That is actually what I have suggested with the 'array' option:) Doing with ADO is easier IMHO given that there is CA now.

I wonder what sort of chaos would ensue if a CA was passed as a parameter to code executing in a different datasession, and then some of the CA's methods were run there - some of those that actually do something (not event hooks, which only react). The CA's attached alias would remain in its original datasession... hm. Time to think and maybe try some.