>Hi Mark
>
>Thanks for responding.
>
>>You could use Pessimistic row or table buffering.<
>
>The view is parameterised so, I don't actually now how many hundreds/thousands of records will be pulled in. However, when my view is populated, I want to ensure that other users will not tamper with the source records that I am processing in the view. Do the buffer modes you refer to, when working with a view, only relate to the data in the view? Remember, I am not working directly with the table. I only want to place a lock on the source data so that the integrity of my processing in the view is not compromised when I finally write the batch of changed records back to the source table.
>
>I can see that using the buffer modes you refer to if working directly on the table would work but I am not sure that the table records would be locked by merely populating the view?
>
>What do you think?

Mark is correct. Remember that a view is always located on the user's PC, so it makes no sense to do locking on the view. When you use pesimistic locking, it will lock the tables...not the view.