Hi!

Hmm, I already made some n-tire things using VFP and never required private data sessions here. Data session in VFP looks weird for me compare to knowledge of OOP and compare to ADO. It is just a weird way to solve problem with cursors hidden for forms. Instead of making object wrapper for cursor, MS VFP Team decided to use such approach. Imagine how better will be if you will not have alias areas, but cursor object in VFP? Now many frameworks have their own wrapper objects. I have my own too, but I never used private data sessions for that. Just use table with alias with unique name generated using sys(3) function - you're there. When functionality built into some object in framework and does not require extra programming for users of that object - it is even MUCH more better than development using some weird session objects used by hacking ways (natural purpose of session object - to use together with forms).

>Vlad,
>
>>...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.
>
>Probably you'll find more uses for private data sessions apart from forms (Session class) as you do more nTier and Distributed application design. An example would be business objects which are completely encapsulated and do not depend on any settings or environmental conditions outside of themselves, allowing them to be called from anywhere.