DataSet hell - "Failed to enable constraints. One or more rows contain values...."

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

Tue, 10 Feb 2009 16:47:17 GMT

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

nateirwin.net » Blog Archive » ASP.NET DataSet Error: "Failed to enable constraints. One or more rows…"

Sun, 02 Nov 2008 19:47:53 GMT

Pingback from nateirwin.net » Blog Archive » ASP.NET DataSet Error: "Failed to enable constraints. One or more rows…"

Programming Links Of The Day, 3/24 « 36 Chambers - The Legendary Journeys

Programming Links Of The Day, 3/24 « 36 Chambers - The Legendary Journeys — Tue, 25 Mar 2008 00:01:02 GMT

Pingback from Programming Links Of The Day, 3/24 « 36 Chambers - The Legendary Journeys

My top 21 Most Viewed Blog posts

Community Blogs — Wed, 27 Feb 2008 08:52:20 GMT

Here are the top 21 viewed pages on my blog in the past year and a half: Essential Software to install

DataSet Constraint Error

Brian Mains Blog — Mon, 24 Sep 2007 02:11:40 GMT

I was dealing with an error about "Failing to enable constraints". I was just added to this

» First rule of blogging: Enable Anonymous Comments Community Hacker - Creating online communities and blogs, By Roy Osherove

Mon, 23 Jul 2007 11:22:27 GMT

Pingback from » First rule of blogging: Enable Anonymous Comments Community Hacker - Creating online communities and blogs, By Roy Osherove

re: DataSet hell - "Failed to enable constraints. One or more rows contain values...."

Juan — Wed, 18 Apr 2007 04:04:41 GMT

Joel solution suited for me. Basically another developer changed the size of the column and when i did refresh schema the XSD didnt get refreshed as well. I went to check column by column and comparing it with my database and fix it up. Now all is cool. Thanks dude

re: DataSet hell - "Failed to enable constraints. One or more rows contain values...."

Ed Giardina — Wed, 11 Apr 2007 16:18:12 GMT

With regards to Darren Wainwright's comments, its because you have a mismatch between the TableAdapter and the specific query with regards to the amount of columns. If your TableAdapter is defined as

Select * FROM table_a

and your specific Fill Method/Get Method / Query is

SELECT field1 FROM table_a

SELECT DISTINCT field1 FROM table_a

and table_a has more than one column,for instance, the exception will be thrown. I saw this by 'previewing' the data with the designer. (Right click on the Query in the designer, and choose preview). The fields not listed in the query were empty, and that's what the exception is barking about. The TableAdapter Query must have the same columns as the individual Queries attached to it.

It makes sense, if you think about it. The Fill/Get method of the TableAdapter is really creating a specific type of DataSet, and if you're missing fields, the binding doesn't work properly.

re: DataSet hell - "Failed to enable constraints. One or more rows contain values...."

iHateSTDs — Fri, 30 Mar 2007 18:05:58 GMT

I had a get statement that would not work with the schema of my table adaptor....after hours of insanity I decided to just add another table adapter based on the query I wanted to use (without the where clause), then added a select query with the where clause to the new table adapter.

On my aspx page dropped in a new ObjectDataSource to use the new tableadaptor and it worked like a charm.

For now on I will create seperate table adaptors for complex select queries.

Hope this helps.

re: DataSet hell - "Failed to enable constraints. One or more rows contain values...."

Dennis Alzoubi — Tue, 20 Mar 2007 17:33:07 GMT

I've got that error when I was using the strongly typed dataset, the solution that worked for me is that I've added "Distinct" keyword in the stored procedures that combine two or more tables in the returned final results while defining a primary key in the dataset.