I suppose... :-)

>Well, maybe to summarize, we could say that using TRANSACTIONS in the manner I've described (as soon as data changes on the form) could be done with no problems if using pessimistic buffering, but it's not a good idea when using optimistic buffering. Is that a fair statement to make?
>
>-Bonnie
>
>>>Hi Erik,
>>>
>>>Your answer about BEGIN TRANSACTIONs locking all underlying records (in addition to your discussion with John in another topic about using TRANSACTIONs similar to the way I have been mentioning) got me thinking about this again and I have another question ... does this "underlying record-locking" occur when you are using views to access the data or is it only when accessing the data directly. Perhaps I don't understand the exact mechanism of the way views actually work, but I was under the impression that the BEGIN TRANSACTION would only affect the view and not the tables that the view is based on. Am I way off base on this concept?
>>>
>>>TIA,
>>>-Bonnie
>>>
>>
>>After the view is TABLEUPDATEd(), the table records that were updated are locked until the transaction ends.