VCursor lock question - 2d try

[Fran=?ISO-8859-1?B?5w==?=ois Van Lerberghe]

Thank you Ivan for this clarification and your suggestion. I must now
discover more about stored procedure.

François Van Lerberghe
Rue Thier Monty, 15 A
4570 Marchin
Belgium


le 9/10/13 8:21, Ivan Smahin <ivan_smahin at paradigmasoft.com> a écrit :

> All that ways are possible.
> If you prefer the second way - no problem to use it.
> The only thing is - when you use kReadWrite cursor - it means nobody else will
> be able to create another RW/RO cursor over the same record (sub)set.
> But that records are still available for updating via NoLock cursors or
> directly (using I_Table interface).
> 
> I think you need something like "atomic" peace of your business logic - do few
> updates against some data without a chance to be interrupted by another
> client.
> I would suggest to move it all into some stored procedure and call that sp
> from your app.