I like Nigel's answer to this.
It's a good idea, especially in team development. That way, when another developer comes in to add something to your code (or you come back to your code 6 months later) you know that you were trying to get it shared or exclusive and don't have to go looking for the SET EXCLUSIVE setting.

If someone has EXCLUSIVE set ON, it doesn't necessarily mean they want all tables exclusively all the time. It may mean that they want them exclusively 90% of the time and don't want to type EXCLUSIVE on 90% of USE statements, but don't mind typing SHARED on the other 10%.

Also, it doesn't necessarily mean the app's creator meant it that way. That's the default setting, so if they haven't SET EXCLUSIVE OFF explicitly somewhere, it's on.

>I do not understand why you would use SHARED? If someone has EXCLUSIVE set, then they need the files EXCLUSIVE. What would be an example of needing the SHARED?
>
>Brenda
>