>Hi Mark!
>
>>>So in short: What is wisdom:
>>>
>>>- Create a procedure file with all the procedures we use (replace the oMethod with is) or
>>>- Keep our current way of working and using an object where we put all our methods. If so, then how do we solve the problem mentioned above?
>>
>>The problem is the oMethod object exists in the default datasession. What I do is pass the DataSessionID to my oMethod.SetFunctions(). In the SetFunctions method, I set the DataSession to the ID passed to it.
>
>Hmm that's a good idea. But we created objects based upon the CustomClass object. Would it be better to create such an object based upon a formobject? Because the customclass object doesn't have a dataenviroment.

Michiel,

The way I handle your problem is to keep the sets in the oMethod object. Then, to have the "sets" set to their proper values in Private data sessions, call the oMethod set method from the Form Datasession BeforeOpenTables method.

Perry