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
[quoted text, click to view] "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?
> >