Controlling Updates in ADO using timestamp/update criteria 
Author Message
 Controlling Updates in ADO using timestamp/update criteria

More often then not, its desired that when you get a recordset to the front
end(with optimistic locking)  play around , and do the modifications...and
finally when you want to commit the changes only to the rows which have not
been changed(updated/deleted) after you fetched the records.

I have tried using both timestamp column in the database as well as setting
the update criteria of the recordset to
adCriteriaUpdCols/adCriteriaTimeStamp , but in all the cases you will not
get any error at the front end if the last row to be commited is unchanged,
though it behaves as expected in the update the error is lost if the last
row is sucessfully updated....

for eg: have 3 rows(say value 1,2,3) fetch all three
3.Meanwhile somebody else updates the first row to 4 so it becomes(4,2,3)
4.You do ur updatation at the front end as (5,6,7) then fire a
rs.updatebatch expected the final rows are(4,6,7) but the error is lost

however, u will get an error if somebody has done (1,2,4) in step3

Any pointers are really appreciated...


Sat, 01 Mar 2003 15:01:33 GMT  
 [ 1 post ] 

 Relevant Pages 

1. How to update datetime field with NULL using ADO update

2. Updating Timestamp value in an ADO Recordset

3. Bound controls not updating ADO with adodc.recordset.update command

4. ADO Data Controls + Using SQL instead of recordset.update

5. VB6,Access97,ADO - Update query doesn't update all records

6. ADo ADD New and Update also Edit Update

7. ADO Update on ADO Data Control

8. Using--After Update-- to update field in table.

9. 2nd SQL Server update after update text field corrupts row - using RDO

10. Updating data to a memo field using SQL UPDATE

11. Using Update to update an Access field

12. TimeStamp Updates


Powered by phpBB® Forum Software