>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.

Hum? Will try this... Thanks