>Hi!
>
>>>But really weird results could be expected when making something like Nadya. I forget about Session object at all so far because it takes much more time for "tuning" of such approaches compare too other work-around approaches without use of session object at all. I did not found any reasons to use session object so far.

I use the session class to create "black-box" objects that manipulate their own data tables. That way, I don't have to concern myself with whatever other tables are already open, and I don't need to worry about putting things back.

>>There's really nothing bad or unreliable about Private Datasessions and calling other objects, you just have to be aware of what's going on when you use them.
>>
>
>Agree. But how much of time requires 'tuning' of such approaches? Much more than time required to develop much more reliable workaround. Messing with dependencies between different objects and their data sessions takes some time...

No tuning required. If I mess with the datasession, I put it back, that's all there is to it. Pretty much the way I treat anything I need to change in the environment. If you do it often enough, eventually you learn to do it right and stop banging your head into the wall! < g >

>>>>>Hi!
>>>>>
>>>>>I never even tried to work with data session by that way because I know a lot of bad things about it. Private data sessions are not reliable in VFP even when used by usual way, what say about manual editing?
>>>>
>>>>What makes you say that private data sessions are not reliable?