Hellen,
thanks for your replay.
So the bottom line is: The only reliable way to determine a network wide
(pessimistic) lock on a row is to let it run into the exception and react on this.
Okay, i can manage that in my application.

Am 15 Sep 2006 um 9:35 hat Helen Borrie geschrieben:

> Use it when you want to check whether the user has *already* started
> to edit the record (with PessimisticLocking true) or has already
> posted an update or delete of this record to the server (with or
> without P.L.) in the same transaction that is yet uncommitted.

___________________________________________________________
Der fr�he Vogel f�ngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de