CommandBuilder ConflictOption fallback

  • Thread starter Thread starter Thomas Weingartner
  • Start date Start date
T

Thomas Weingartner

I've already read the post about "CommandBuilder ConflictOption usage"
http://groups.google.ch/group/micro...k=st&q=ConflictOption&rnum=1#3519015bed9c9ba2

Because this option is new, I tried out some of the options:

CompareAllSearchableValues:
- Behaves always independent of the table.

CompareRowVersion:
- Takes the Timestamp column if one exists. If no Timestamp column
exists, it will fall back to "OverwriteChanges". This behaviour isn't
described in the help.

OverwriteChanges:
- Uses PrimaryKey if one exists, else falls back to
"CompareAllSearchableValues" as described in the help.


The default option of the SqlCommandBuilder is
"CompareAllSearchableValues". This isn't described in the help.


MS, can you please confirm the behaviour!


Thomas
 
Sounds right to me. I wrote an article on this (www.betav.com/articles.htm)

--
____________________________________
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)
Between now and Nov. 6th 2006 you can sign up for a substantial discount.
Look for the "Early Bird" discount checkbox on the registration form...
 
Back
Top