Hi Tim,

i'm running an app with DBISAM 4.29b3, sharing "data" directory among 3 PCs.

In certain circumnstances, when a client locks a record for long periods of
times, another client shows this error during routine operations on the same
table involved (refreshes, filters, etc.).

The problem does not occur always, unfortunately.

Any suggestion or workaround?

Thanks
Max

"Max" <max@nospam.com> wrote in message
news:824488F1-5898-40B5-A440-D362A11FDA1C@news.elevatesoft.com...
> Hi Tim,
>
> i'm running an app with DBISAM 4.29b3, sharing "data" directory among 3
> PCs.
>
> In certain circumnstances, when a client locks a record for long periods
> of times, another client shows this error during routine operations on the
> same table involved (refreshes, filters, etc.).
>

It is probably related to pessimistic locking. Is that what you're using?
(look in session)

Robert

Max,

<< In certain circumnstances, when a client locks a record for long periods
of times, another client shows this error during routine operations on the
same table involved (refreshes, filters, etc.). >>

Are you using any 3rd-party grids or multi-line controls ?  Are you sure
that the client that sees the error is not also editing a record ?  A record
lock on one client will not cause a record unlock error on another client.

--
Tim Young
Elevate Software
www.elevatesoft.com