SqlCommandBuilder and optimistic concurrency

  • Thread starter Thread starter KShvats
  • Start date Start date
K

KShvats

Hey ya,

Using .NET 2.0 and SqlCommandBuilder, say I have a customer row, with an
address and name fields. I need 2 different clients to be able to change
1 field each and not get ConcurencyExeption on 2nd Update(). Is it
possible to do?

Thanks
 
Becouse it saves a lot of time, I've got absolutely no performance
problems and a lot of things to do.
 
KShvats,

You can use the SQLCommandBuilder's ConflictOption property to specify how
to deal with concurrency violations.

However, the choices may not be fine-grained enough for your needs. In that
case I think you will need to supply your own SQL statements for Insert,
Update and Delete.

Kerry Moorman
 
Back
Top