Home All Groups Group Topic Archive Search About
Author
12 May 2006 2:05 PM
marcmc
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.

Author
12 May 2006 2:11 PM
Chris
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
Author
12 May 2006 2:16 PM
Kerry Moorman
marcmc,

Does the table have a primary key defined?

Kerry Moorman


Show quoteHide quote
"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.
Author
12 May 2006 2:22 PM
marcmc
yep and a unique clustered index
Author
12 May 2006 2:24 PM
marcmc
i dropped the unique clustered index and now the message is "There were
errors configuring the data adapter."
Author
12 May 2006 2:23 PM
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

Show quoteHide quote
"marcmc" <mar***@discussions.microsoft.com> schreef in bericht
news:0825DCB0-D219-4EAC-BF96-B3864D7BB5D2@microsoft.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.
Author
12 May 2006 2:33 PM
marcmc
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?
Author
12 May 2006 3:13 PM
marcmc
anyway, does anyone know how to solve this?
Author
12 May 2006 3:51 PM
coen
marcmc wrote:
> anyway, does anyone know how to solve this?

I also think you must configure your DATABASE to have a primary key.
Author
12 May 2006 4:32 PM
Cor Ligthert [MVP]
Most likely is the key not a part of your select statement.

Cor

Show quoteHide quote
"marcmc" <mar***@discussions.microsoft.com> schreef in bericht
news:BBC8EC13-D856-4478-B6B7-A6DF0C16E2A7@microsoft.com...
> anyway, does anyone know how to solve this?
>