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

Re: SqlCommandBuilder and optimistic concurrency by Miha

Miha
Mon May 21 05:51:03 CDT 2007

Why don't you craft your SQL statements manually instead of using builder?

--
Miha Markic [MVP C#, INETA Country Leader for Slovenia]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/

"KShvats" <z@z.z> wrote in message
news:udQUmV5mHHA.3520@TK2MSFTNGP04.phx.gbl...
> 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


Re: SqlCommandBuilder and optimistic concurrency by KShvats

KShvats
Mon May 21 07:16:46 CDT 2007

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

Miha Markic wrote:
> Why don't you craft your SQL statements manually instead of using builder?
>

Re: SqlCommandBuilder and optimistic concurrency by KerryMoorman

KerryMoorman
Mon May 21 09:19:00 CDT 2007

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


"KShvats" wrote:

> Becouse it saves a lot of time, I've got absolutely no performance
> problems and a lot of things to do.
>
> Miha Markic wrote:
> > Why don't you craft your SQL statements manually instead of using builder?
> >
>