That's a good point. If you simply USE table, the DBC will be opened with it. However, a good practice is to OPEN DATABASE x SHARED before any USE statements.

>You remember correctly and Cyrus should be aware of the point you've made. Nevertheless, table and database containers are at different levels. When the database is opened excusively, it's the access to the container that is denied and that does not look like Cyrus' scenario: if a database container is openend exclusively there is no way another user or process can open any of its objects as shared resources.
>
>And going back to the first question Cyrus posted, what applies to tables also applies to databases: even if SET EXCLUSIVE is ON, you can OPEN DATABASE x SHARED and it will be opened in non-exclusive mode.