Saturday, 21 February 2004, 9:51 AM
Hi Helen,

HB> The pessimistic lock does that. If IBO can't get the lock, it won't let
HB> the row go into Edit mode. You can catch the exception and use it to
HB> inform the user that someone else is working on it.

That's what I currently do, but I was wondering if there was a way to
not use pessimistic locking, but still give a similar message and
allow the operator to continue on and edit the record?

HB> OTOH, if you use the "quick transaction" approach with Read Committed and
HB> WAIT, there will be no exception if the later transaction has a higher
HB> transaction ID on the server. First to get the lock wins, others follow on
HB> in "hit order".

hmmm, I will have to sink my brain into this one, but right now it's
too hot here for that! :)

thanks
Mark

HB> Helen



HB> ___________________________________________________________________________
HB> IB Objects - direct, complete, custom connectivity to Firebird or InterBase
HB> without the need for BDE, ODBC or any other layer.
HB> ___________________________________________________________________________
HB> http://www.ibobjects.com - your IBO community resource for Tech Info papers,
HB> keyword-searchable FAQ, community code contributions and more !
HB> Yahoo! Groups Links