Calvin,

The oApp object isn't scoped to any data session. Like all other code it operates on whatever the current data session is. If you call it from a form with a private data session it will be operating in that form's data session. You could always change your code to have it save the current data session, set the data session to default, check the value of cust.type, then set the data session back to the saved value.

>At start up I create an application object - oapp. In this object I have a method that operates on data- something like:
>
>if cust.type='Business'
> return something
>else
> return soemthing else
>endif
>
>which is manipulating data in an open table. If the form this is called from uses a private datasession then the method does not see the cust table. In other words, it appears that the oapp object is scoped to whatever datasession was active or the default when the object was created. Is this right or have I just messed up somewhere? If it is right, why was it designed this way? I am perplexed.