please help... multiple key table and merge

  • Thread starter Thread starter Aaron Lind
  • Start date Start date
A

Aaron Lind

I have a table with 3 keys, it is possible that the user may want to
change one of them. If the key is changed (let's say from 1 to 2) the
actual update to the database works fine. The problem is that when
the dataset gets back to the client and an attempt is made to merge
with the original dataset, an error is thrown:

"Failed to enable constraints. One or more rows contain values
violating non-null, unique, or foreign-key constraints."

Basically, the original data appears to assume the original key value
is 2 when it is really 1. It seems to me that I should be able to do
this. The row is in a modified state so the 2 value should not be
considered the current key. Any suggestions would be greatly
appreciated.

Aaron
 
I was just thinking. Am I over merging? Up to this point I have only
worked with Identity primary key tables. Is merge only necessary in
Identity key scenarios as well as merging different record sets
together?
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Dataset constrain error 2
merging deltas 4
Dataset constraint violoation with null foreign key value 6
Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign 1
Saving Master-Detail bound form - primary key is identity column 2
Default DataTable Constraints with SQL Server 2000 vs 2005 4
VS2005 Strongly Typed DS and Mutliple Result Set 1
Failed to enable constraints but please tell me sth. 6

Back
Top