>>>Every copy of a view you open will open exclusively, but that's ok, because a view isn't a shared resource. (A view definition is). Don't worry, your app will be fine.
>>
>>Okay, then maybe I'm not really understanding what's going on. I was doing multi-user testing the other night on the app and was getting a lot of "you can't have it, someone else is using it" messages. So that's when I found that the views were opening exclusively. And that's when I figured that must be the problem. Is there something else I should be looking at? Thanks.
>
>There is no such things as having exlusive access to a view definition. You have exclusive access to the view, yes, but that's because the cursor that your view creates is its own copy that lives on your disk (or in your memory), and noone else can see it.
>
>Your contention problems lie else where. What are the exact errors you are getting, and when?
I bet that she was switching to another session on her machine and running the app again?
__Stephen
