>>>>A view is always opened exclusively, regardless of the lock status of the underlying table(s).
>>>
>>>So a view shouldn't be used in a record search procedure if the environment is multi-user?
>>
>>Fundamentally, a view is just the result of a SELECT - SQL statement. Its contents are valid as at the instant it was opened.
>>
>>You can refresh a view's contents (basically cause its underlying SELECT - SQL to be run again) by using the REQUERY() function.
>>
>>If you REQUERY(), you don't need to regenerate your indices, they will still be in effect.
>
>Am I right in my thinking -- If person1 is using a form with the view in its D.E., a person at another workstation can't use the form person1 is using because it calls the same view (which is opened exclusive)

No, that's not correct. A view is a local cursor. Conceptually it's the same as a SELECT - SQL result cursor, except that it can be made updateable. In your example, each workstation would get a local cursor created on their machine. These cursors are completely independent.