471,066 Members | 1,242 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,066 software developers and data experts.

DataAdaptor Bug!

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.
May 12 '06 #1
9 1031
marcmc wrote:
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
May 12 '06 #2
marcmc,

Does the table have a primary key defined?

Kerry Moorman
"marcmc" wrote:
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.

May 12 '06 #3
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

"marcmc" <ma****@discussions.microsoft.com> schreef in bericht
news:08**********************************@microsof t.com...
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.

May 12 '06 #4
yep and a unique clustered index
May 12 '06 #5
i dropped the unique clustered index and now the message is "There were
errors configuring the data adapter."

May 12 '06 #6
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?

May 12 '06 #7
anyway, does anyone know how to solve this?

May 12 '06 #8

marcmc wrote:
anyway, does anyone know how to solve this?


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

May 12 '06 #9
Most likely is the key not a part of your select statement.

Cor

"marcmc" <ma****@discussions.microsoft.com> schreef in bericht
news:BB**********************************@microsof t.com...
anyway, does anyone know how to solve this?

May 12 '06 #10

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

16 posts views Thread by Edward Diener | last post: by
158 posts views Thread by Giovanni Bajo | last post: by
reply views Thread by Kurt B. Kaiser | last post: by
reply views Thread by LiveTecs | last post: by
12 posts views Thread by Juan T. Llibre | last post: by
reply views Thread by leo001 | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.