I see...
Cathi what about refreshing the dataset is there a way to do it, is my way is correct?


>Because of issues with the Command Builder, it should only be used when generating very simple queries. I would not recommend using it for updating for the problems you are experiencing. It doesn't handle concurrency very well.
>
>>I'm using CommandBuilder !
>>
>>
>>>You are experiencing this because of your SQL Update statement. Your statements must be able to handle concurrency issues. I would recommend using store procedures to perform your updates. You will have better control over how the updates occur.
>>>
>>>>Thank u Cathi,
>>>>
>>>>But I having this error,
>>>>"Error #5, Concurrency Violation:..."
>>>>and this happen when I add the new row then update my DS then try to modify it again!
>>>>I this I should Re-Fresh or Re-Fill the DS, if yes, that means I should do the Re-Fill after each add, delete or modify operation I do?
>>>>And will this code do the job:
>>>>
>>>> ' Update DataSet
>>>> Me.BindingContext(myDS, "Area").EndCurrentEdit()
>>>> myDA.Update(myDS, "Area")
>>>> myDS.AcceptChanges()
>>>>
>>>> ' Re-Fresh DataSet
>>>> myDS.Clear()
>>>> myDA.Fill(myDS, "TableName")
>>>>
>>>>Thanks again