snip..

>I, for one, hate automatic things occuring. If I want pessmistic strategy I use Optimisitc Table buffering and I deal with the locking. The buffering gives me the easy ability to edit fields directly and later decide to save or discard the edit. The optimisitc gives me no automatic locking except for during the save operation. The table buffering prevents any unexcepted updates from happening automatically because some code moved a record pointer.
>
>Using Opt Table buffering, I can implement either the optimistic or the pessimistic strategies for multiuser contention resolution. If I use pessimistic buffering I am locked into the pessimisitic strategy. Since buffer modes dictate how other code needs to be written, I prefer to globally use the same buffer mode for everything and write code to implement the appropriate strategy.

Jim,

I'm using this same strategy of optimistic buffering with manual pessimistic locking. Got any feedback on how to do this with views? If you have a chance, please take a look at thread #165016 from today and answer there. I'm new with views. Thanks in advance.