>My solution to the problemw was to issue a 'Set datasession to 1' in the oapp.openshared() method. This fixed the problem. However, the question remains- Why did the data session switch to #4 inside this object method when the object was created with session #1 active and an explicit set datasession to 1 had been issued prior to calling oapp.openshared(). I just need some glimmer of a reason for this to happen to be satisfied.

Open the debugger and set a breakpoint on when SET("DATASESSION") = 4