>>>So if you want the user to be able to open the same form twice you need private datasessions. I still don't see what it has to do with buffering.
>>
>>I meant, that you need in private DS, only if you use buffering. If you don't use buffering, then you don't need in private DS.
>
>Why? I don't see that at all. I would use private data sessions whether or not I am using buffering, whether or not the application is single or multi user, whether or not it is in English or Chinese. Private data sessions give us a major leg up on creating event driven applications and not to worry about things like record pointers between forms.
>
>I'm sorry, I don't understand the link here.

It's probably depends on interface's approach. I didn't mean that you must not use private datasessions. I just tried to highlight that if you have row buffering and want to navigate in real windows interface with many forms open concurrently then private DS is 99% requirement. If, for some reason, developer doesn't want to use private DS, then s/he should reconsider interface approach, e.g. eliminating buffering.
Just let me repeat one more time, if someone wants to use privateDS that's fine, I have nothing against it, but there are other ways which are probably good too.