Hi Helen,

an "explicit" lock (or pessimistic lock):

SELECT * FROM {table} WHERE {whereclause} WITH LOCK;

prevents the record from being changed by other users at the same time
(getting a lock conflict-message, which is ok).

If the PC is turned off however, this LOCK remains on the serverside,
so the only way to "free" the record is by restarting the FireBird server.

There seems to be no other way to release this lock ?

thanks
Glenn

--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...> wrote:
>
> At 07:37 PM 25/04/2008, glenndetollenaere wrote:
> >Hi all,
> >
> >I have the following question:
> >our application uses FireBird as database, residing on a server. If we
> >do an explicit LOCK on one of the clients, and the PC has been turned
> >off (or network has been cut off), the lock stays on the server. In
> >that case the FireBird server needs to be restarted completely to
> >delete that lock (it stays "hanging") ?
> >
> >Is this a known issue, can it be solved by any means ?
>
> Is "what" a known issue? What do you mean by "explicit LOCK"? What
do you do to accomplish it? What happens when you do it?
>
> ./heLen
>