Re: BatchOptimistic Locking

From: Stephen Howe (stephenPOINThoweATtns-globalPOINTcom)
Date: 03/24/04 

Date: Wed, 24 Mar 2004 12:25:20 -0000

news:OMrXXxUEEHA.2600@TK2MSFTNGP09.phx.gbl...
> Does batch optimistic locking does not raise an error
> when we delete data in recordset which the underlying data has been change
> since it was read?

I think it will. If you afterwards iterate over your Recordset, the Status
value of that record will be different. I think the following bit will be
set

adRecDBDeleted for records that are already deleted.

(see http://www.w3schools.com/ado/prop_rs_status.asp)

Stephen Howe

Relevant Pages

  • Re: The data has been changed. Another user edited this record and saved the changes before you atte
    ... > when I change field2 on the form, ... Why are you using a separate recordset to update data that is ... already opened in the recordset behind the form you're using to edit ... than the obvious method of changing the form's underlying data, ...
    (comp.databases.ms-access)
  • Re: The data has been changed. Another user edited this record and saved the changes before you atte
    ... when I change field2 on the form, ... Why are you using a separate recordset to update data that is ... already opened in the recordset behind the form you're using to edit ... than the obvious method of changing the form's underlying data, ...
    (comp.databases.ms-access)
  • Out-of-process recordset
    ... I have an out-of-process server that implements an object ... with a "Recordset" property, implmented as a read-only IDispatch* property. ... This does not change the field value in the object's underlying recordset. ... controls and the underlying data in never changed. ...
    (microsoft.public.inetsdk.programming.scripting.vbscript)
  • BatchOptimistic Locking
    ... Does batch optimistic locking does not raise an error ... when we delete data in recordset which the underlying data has been change ...
    (microsoft.public.data.ado)
  • Re: How do I check if recordset exist?
    ... I wouldn't bother checking, I'd just try to close it and ignore the ... error this may raise: ... >whether recordset is exist or not? ... John Nurick ...
    (microsoft.public.access.gettingstarted)