>Hi Ed,
>
>>a form must operate in the context of a single session.
>
>Yes I know this, but i need to access to another datasession.
>
>>you migth try creating something based on a session object subclass - set up the session object with a private datasession, and do whatever is needed in methods of the session - that way the form retains its default datasession.
>
>No I can't, the object is a DBCX2 metaobject that creates a second datasession, if i instantiate a subclass of this, i would get another sessionid again, if the only drawback is having to code again the recordsource & column controlsource, I'll do it, knowing this isn't a good way.
>

It still might work - create a Session subclass, save the DBCX2 datasession id to a property in the Session subclass, and do all the munging about in the session object, including doing the SET DATASESSION TO - again, the form's datasession doesn't get touched that way.