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

Question

0.00/5 (No votes)

See more:

I'm using a TableAdapter which references an Object Data Source and it's code is in a BLL code.

When it runs, i get:

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

I looked at all of the data and there are no duplicates on the primary key field, no null or blank fields and all fields have AllowDBNull=False.

I deleted the datatable and recreated it by dropping the table from the database on to the dataset.

I tried setting EnforceConstraints=False

I read dozens of forum posts here about this subject and cannot figure out why this is happening. All i want to do is populate the dropdownlist with a set of unique warhouse numbers.

Any help would be gratefully appreciated.

Posted 13-Nov-14 0:23am

User 10878480

Updated 13-Nov-14 0:29am

Thanks7872

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Deepu S Nair · Answer 1 · 2014-11-13T01:17:00

This problem is usually caused by one of the following

*null values being returned for columns not set to AllowDBNull
*duplicate rows being returned with the same primary key.
*a mismatch in column definition (e.g. size of char fields) between the database and the dataset
Try running your query natively and look at the results, if the resultset is not too large. If you've eliminated null values, then my guess is that the primary key columns is being duplicated.

Or, to see the exact error, you can manually add a Try/Catch block to the generated code like so and then breaking when the exception is raised:

Also you can use SQL Server Profiler so that you can find where the error actually occurs.