SET EXCLUSIVE OFF is the default for private datasessions, so unless you have specifically SET EXCLUSIVE ON somewhere, this is not your problem. Another possible but source of 'exclusiveness' id the DE.Cursor.Exclusive property. But this is set to .F. as a default as well.

What error do you get when trying to open the form?

In the form that you believe has the table open exclusively, have you checked ISEXCLUSIVE() for the table in question? I mean are you positive that this is the problem?

>Eric ---
>
>Since the datasession is private, you have to set the environment (including SET EXCLUSIVE OFF, which is probably your problem) for each datasession. Try putting SET EXCLUSIVE OFF in the Load of the Form or in the BeforeOpenTables event of the DataEnvironment.
>
>
>>I'm working on a set of apps that will share a database in a common location for maintenance and user/security information. The .dbc is opened shared by each app and is provided a path to the data. This works fine if I'm using controls loaded by sql or only do lookups or inserts etc. The problem comes when I try to open a form with a common table in the DE. If one form is open in appA with the userid table in the DE, a similar form in appB using the userid table in the DE will not instanciate. The datasession in both cases is private. Forms used in any of the apps in this group run normally as long as they do not have any of the common .dbc tables in thier DE. I'm not sure how this type of sharing is best implemented.
>>
>>TIA,
>>
>>Eric K.