I'm having a strange problem with auto generated datasets.
I'm using a Sybase database. I have a design time dataadapter, with a simple select statment, and then I generate the dataset. All goes Ok.
When I run my app, I get a 'Failed to enable constraints' error, on the MyDataAdapter.Fill(MyDataSet).
The select statment is correct, I have a primary key defined on both the database and dataset.
The full error is:
'Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints.'
The primary key has no null values, nor non-unique. I have no foreign-keys.
I've had a similar problem on a VB.NET app, with different tables, and different database engines.
Is this a problem with .NET design time datasets? Is there a solution?
Any ideas?
NetAngel
I'm using a Sybase database. I have a design time dataadapter, with a simple select statment, and then I generate the dataset. All goes Ok.
When I run my app, I get a 'Failed to enable constraints' error, on the MyDataAdapter.Fill(MyDataSet).
The select statment is correct, I have a primary key defined on both the database and dataset.
The full error is:
'Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints.'
The primary key has no null values, nor non-unique. I have no foreign-keys.
I've had a similar problem on a VB.NET app, with different tables, and different database engines.
Is this a problem with .NET design time datasets? Is there a solution?
Any ideas?
NetAngel