>>It can be kept simply, since you put exclusive access on table nobody else can >access this table. So, it's question of error handling, I mean when users >launch an application and try to get shared access they should get nice message >and quit.
>
>The case I was concerned with was this: user needs to pack/reindex, N people have it opened for shared already - how does one handle securing exclusive access in an elegenat and robust way?
>
>
>Tim

This way, this user will get 'stop' message. Do you want to force other users to quit?