>>But the point is that I don't use buffering :-).
>>
>>
>>>In fact, the only time I see a default data session having any value is when I have a child form that must manipulate its parent's data directly.
>>
>>I would say, it depends. It's very probable that in your framework it does not make value. Personally, I like it, it greatly simplifies for me SET PATH issues (actually I don't have to use it at all), maintenance form (PACK/REINDEX) closes/opens data handily (two methods of the only DE I have), many other minor things. Again, it's really developer-specific issue. I would not make any general claims here.
>
>Ed,
>
>So you don't use private data sessions, and you don't use the form's DE, and you don't use buffering, and (really important for me) you recommend to others that this is the way to do things. Ed, I hate to say this but it sure sounds like you are writing FP 2.x code in VFP. Are you using scatter and gather to allow for reverts of data edits?
>
>BTW, in another message you described the exact methodology that you are using to save and restore the state of the data environment.
>
>Also, maybe you didn't know, private data sessions do NOT require the use of the DE. You can set a form to a private data session and then write USE commands in the Load to open the tables. The form will have a fully encapsulated and protected data session without you writing any code anywhere to manage or protect that data session from encroachment from any other form.

Firstly, I use DE, one located within top-level form. Secondly, I use SCATTER to object.
I hate to say it, but it seems that you see what you want to see, too strongly,