>Hello Charlie
>
>well, '...to debug forms' - ja - i read that in the help too, problem is the debugger is lying (see discussion in this thread), it says i am in the private ds, when actually i am not.
>
>you suggestion was mentioned earlier in this thread, and it looks like thats what i am gonna have to do :-(, but i don't like it.

I've seen a lot of code where the datasession is passed as a parameter... like this:

	procedure exec(nDS)
n=set("datasession")
set datasession to (nDS)
{bla bla}
set datasession to (n)
return

The reason for this is that any object's code will execute in the datasession which was active when the object was created. So switching datasessions is OK, IMO - I'm doing it every day, it just needs to be done at the method level, or you have to create objects in the DS where you want them to execute.

Now Dorin may be up to something... if just storing a reference to an already created object as a property of the current object, and then calling it using this reference makes it run in the caller's datasession... that'd be cool. I'll have to check that, sounds too good.