(update to my previous answer)

It makes a difference whether the object is 'added' to the form using addObject() - becoming a form member - or addProperty():
- using addObject() makes the object participate in the form's dataSession
- using addProperty() keeps the object independent from the form's dataSession

>Here's what I'm finding...
>
>Any object in FoxPro that runs a query, whether against native DBFs or Sql Server, will create the cursor in the DataSession which was active at the time the object was created.
>
>The means that if you have a BO created in Form A with a Private DataSession, and you pass that object to Form B which has its own Private DataSession, if you use the object to run a query from Form B, the cursor will be created in the DataSession from Form A.
>
>Crazy! But true. It took be about an hour of stepping through the codez to figure this out.
>
>Does anyone know a work around, or a pattern to avoid this??
>
>
>.