Yet another "Concurrency violation: the UpdateCommand affected 0 records" exception

[Santi]

Hi friends,

In an application with a single user - single computer, with
InsertCommand and UpdateCommand created by hand, and a FoxPro database
accessed with OleDB, when following this steps I get the exception:

1. Insert a row in the dataset OK
2. Call to Update, the row is inserted in the database OK
3. The inserted row is modified in the dataset OK
4. Call to Update, the row is not updated, concurrency exception
appears KO

Any help?

Thank you.

 

[William \(Bill\) Vaughn]

Are you modifying the PK?

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)

 

[Santi]

I already get with the solution.

The problem was that I was not initializating a field in the moment of
inserting the row in the dataset. Then when this row was inserted in
the bd, the bd assigned a default value to that row. Finally when
updating the new changes both rows (dataset and bd) where different
and then the concurrency violation.

Thanks anyway!