Hi,

If I run an SQL update statement on a table, what happens when it comes
across a record that is being used by another user?  Does it update all the
other records or does the statement stop at the point it cannot update a
record and not perform the rest of the updates.  DBISAM V3.30

Thanks

Alex

Al


I think this is where you need transactions. My understanding is that the changes will be made up to the point where it can't lock the record where it will crash.

Roy Lambert

What locking model are you using: pessimistic or optimistic?

Regards,

Jason Lee

Al Vas wrote:
> Hi,
>
> If I run an SQL update statement on a table, what happens when it comes
> across a record that is being used by another user?  Does it update all the
> other records or does the statement stop at the point it cannot update a
> record and not perform the rest of the updates.  DBISAM V3.30
>
> Thanks
>
> Alex
>
>

Alex,

<< If I run an SQL update statement on a table, what happens when it comes
across a record that is being used by another user?  Does it update all the
other records or does the statement stop at the point it cannot update a
record and not perform the rest of the updates.  DBISAM V3.30 >>

You'll get a record lock error if DBISAM cannot update any single record
that it needs to because it can't get a lock, and the update will stop at
that point.

--
Tim Young
Elevate Software
www.elevatesoft.com