>Thank you for your response. It works great as an app. No problems. I have found the problem, and have a theory. Correct me if my theory is wrong.
>
>You can set exclusive off, but when a table is opened that is contained in a database, the table is opened shared, but the database defaults to opening exclusive.
>
>My work around is to open the database shared before opening any tables. This works great. I tried it just to see, and when it worked I was surprised. I had always been under the assumption that set exclusive affected both databases and tables.

In my apps, I always open the DBC before any table. However, I do not see the same type of behaviour as you do. I can open a table that is part of a DBC, but the DBC opens shared if I have EXCLUSIVE off. I only get the behaviour if exclusive is on.

If you are using your own form class with private DS, do you have all the necessary SET commands in the form's LOAD method? Also, if you open tables in a DE environment, you need to start with the usual SET commands.

set talk off
set exclusive off
set multilocks on
set deleted on

Just to cover everything, a list of all SET commands that are scoped to every data session can be found in VFH Help under SET DATASESSION.