>>>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...
>
>Hello, Vlad.
>
>I can't understand your point. Don't you use private datasessions in your forms? As soon as I discovered the Session object I started using it for a lot of non-visual code. The usage is almost the same that in forms.
>
>May be you feel it unreliable because you tried to aplly it to a specially complicated case. I use it instead of the custom class, and indeed changed to it some older code because it is far easier to encapsulate behaviour.
>
>Give it another chance!

Hi!

I use private data sessions very often, mabe even more than others, though I faced a lot of problems as well.

The 'tuning' I mentioned above is related to separate session object created separately from form or created based on the custom session object. I never used this approach because there are a lot of ways in VFP for doing the same thing and I had never situations I need handle session object. I never used private data sessions more than just setting form's property to use it.