Michiel,

I see JimB already showed you how to add your custom object to the form. The only object I ever instantiate in the default datasession is my oApp object. It never does anything that is DS related, it only maintains other globals like Help, the _screen and the menu. So none of the potentially hazardous changing datasessions ever happens in my app.

>That's correct. IF it were a method from my form class. But we use an CustomObject where we put all our methods. And if we call a method which containts SET commands from our customobject via a private datasession form when the SET commands won't work in that private datasession form.
>
>Somebody suggested to change the current datasession from the Custom object to that of the private datasession. This worked fine. But we don't know when the form is released in WHICH datasession the customobject is. Did it go back to the global datasession or??