Re: locking in ADO
From: Susan Leigh (magine_at_turtleflight.com)
Date: 02/21/04
- Previous message: Brian Bushay TeamB: "Re: 'Blob' problem.Thanks."
- In reply to: Brian Bushay TeamB: "Re: locking in ADO"
- Next in thread: Jeremy Collins: "Re: locking in ADO"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 20 Feb 2004 21:08:18 -0500
No, Optimistic locking. As far as I know (and intend) all the database
access is serial...no new operation should begin before any previous one
is done.
Brian Bushay TeamB wrote:
>>The errors I'm seeing are either:
>>
>>Could not update, currently locked by used 'admin' on machine 'TORTUGA'
>>
>>(Tortuga is the computer's name.)
>>
>>OR
>>
>>Row cannot be located for updating, some values may have changed since
>>it was last read.
>>
>>Is this a matter of trying to change too many records in rapid
>>succession?
>
>
> No. The second Error occurs when ADO can not find the record in your dataset in
> the database to update it. The default is to use all the field values from when
> the record was retrieved. Your fields no long match what is in the database.
> I have never seen the first error you are getting. Are you trying to use
> pessimistic locking or do you have a transaction open?
> --
> Brian Bushay (TeamB)
> Bbushay@NMPLS.com
- Previous message: Brian Bushay TeamB: "Re: 'Blob' problem.Thanks."
- In reply to: Brian Bushay TeamB: "Re: locking in ADO"
- Next in thread: Jeremy Collins: "Re: locking in ADO"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|