>Well, there are also lots of time when I do it the same way you do - by passing a data session id and switching into the required data session. I do that when lots of data is incolved, for example, with my audit logging class. We also use that technique extensively in the data classes < s >.

Yep, I noticed that.

I get nervous about switching, because if a menu or a form is bound to data in the private session via SKIP FOR in the menu or a bound grid on the form and somehow it decides to refresh while the datasession is switched, things go awefully wrong (as I'm sure you know).

Ever noticed that even the debugger menu will trigger a re-evaluate of SKIP FORs of _msysmenu? So if your form makes a call to a private datasession, and you get a bug in there, and you have something like SKIP FOR EOF('MyData') in your menu, and MyData is not available in the private session, you can't click on the debugger menu. Lots of fun :-)