If you use pessimistic locking then what happens is it produces a "lock"
which is merely a dummy update on the record which reserves it for future
modification by the current transaction and prevents other transactions from
modifying that record until it commits or gets rolled back. So, when another
user in another transaction tries to take a dataset into edit state and it
attempts the dummy update it will get a deadlock. Then, I raise an exception
preventing from going into edit state and display an error message that
another user has a lock on the record.

HTH,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "Regis" <regisw@...>
To: <IBObjects@egroups.com>
Sent: Wednesday, January 10, 2001 12:05 PM
Subject: Re: [IBO] Locking records


>
> > Checking if a record is locked isn't really a concept that will work for
> > you.
> > The closest thing is to use the PessimisticLocking property of the
> datasets.
> >
>
> Excuse me, but what exactly do you mean by this ?
> I understand that there isn't a simple method to do it , I have to use
> deadlock exception catching . Yes ?
>
> Regis
>
>
>
>
>
>
>
>