Hi Stuart,

I had exactly the same problem. I could not find any useful
workaround. So I changed from pessimistic locking to optimistic
locking. It was a little work, to change my whole application, but now
I am happy with this solution.

The reason, why I first used pessimistic locking was, that I hate to
let the user change data and then tell him, that he could not save the
data, because it is locked. Now I found a way, to go around this
problem. When a user wants to save the changed data, the application
trys to save, and in case of a locking error, it rereads the data and
changes only the fields, which were changed by the user and saves it
again. This works pretty good.

cu
Helmut