>You might be able to test this on your development computer. Start an instance of the APP. Minimize it. Start VFP. Open the debugger and place a breakpoint when the value of SET('EXCLUSIVE') changes. DO the APP either in the debugger so you can trace line by line or from the command window.
>
>Also, make sure you do not have EXCLUSIVE=ON in a CONFIG.FPW file that may be being used.
>


Mark,

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.

Again, thank you for your idea. I will be checking the config.fpw just to make sure that that didn't cause the problem. I hate to add extra code when it is unnecessary.

Thanks!