Not enough. A private datasession will use the default settings, so in that datasession, you'll have EXCLUSIVE ON. If you lookup Private Datasessions in Help, you'll see which SET values are affected. The solution is to reset the SETtings in the DataEnnvironment BeforeOpenTable event.

>Dear all,
>
>Can another have a evaluation on my setting:
>
>I implement an application included 2 computers on LAN, a set of tables to be shared.
>
>All I have do isn,t like this?
>
>SET EXCLUSIVE OFF
>SET MULTILOCKS ON
>DATASESSION = 2
>DATAENVIRONMENT.CURSORx.BUFFERMODEOVERRIDE = 5
>
>Is a shared system completed?
>
>And is that true that th eworst thing is that I edit th esame record of the same table at the same time ?
>
>The case is urgent !
>
>Thank you for your attention.
>
>With Regards,
>
>Ransome