>Dear Peter,
>
>Private datasession gives to us facility tune differents database environments on one computer like differents computers. For example, when you want open two or more the same windows with customer's information - in this case you can work in every windows as with independent windows. And you can open windows as much as you want and limitation - only your free PC's memory (and you can update date using # of current datasession).

Thanks for answering.

I basically understand private datasessions. All of my forms use them.

My question is whether there is some kind of problem if I also update my tables in the default (number 1) datasession without using buffering. Assuming that the tables are not locked would this interfere with an update in a form using a private datasession?

I've also seen (but haven't pinned down) interaction between two different terminals when they have the same parent record on the screen. The form is using a PD. This interferes with updates but I don't understand why.

Peter