DataAdaptor Bug!

[Guest]

When I configure the dataAdaptor i get "Could not determine which columns
uniquely identify the rows for TableName" and so the update and delete
statements are not built.

 

[Chris]

When I configure the dataAdaptor i get "Could not determine which columns
uniquely identify the rows for TableName" and so the update and delete
statements are not built.

Do you have a primary key set?

Chris

 

[Guest]

marcmc,

Does the table have a primary key defined?

Kerry Moorman

 

[Guest]

yep and a unique clustered index

 

[Cor Ligthert [MVP]]

Marc,

What do you mean by bug, is that to let the Microsoft people not look
anymore to these messages. You hide now real bugs with your message. So
please write only about a bug when you sure it is.

I will spare you how most active persons in this newsgroup call your
question.

Cor

 

[Guest]

i dropped the unique clustered index and now the message is "There were
errors configuring the data adapter."

 

[Guest]

Cor,
I apologise if I have broken any of the guidelines or rules regarding my post.
I have changed the title to DataAdaptor Issue.
I'll be honest I was hoping that the title would encourage more people to
look at it.
I've been using Microsoft.public on a number of different technologies for
many years and am unaware of any rule about this. Maybe you can clarify? Is
it a known issue? Is there a recommendation to solve?

 

[Guest]

anyway, does anyone know how to solve this?

 

[coen]

anyway, does anyone know how to solve this?

I also think you must configure your DATABASE to have a primary key.

 

[Cor Ligthert [MVP]]

Most likely is the key not a part of your select statement.

Cor