469,578 Members | 1,298 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,578 developers. It's quick & easy.

Generated UPDATE statement. could not determine which columns uniquely identify the rows for "Customers"

i am having trouble updating a datset because i get the follwing error
in the Data Adapter configuration Wizard:

Generated UPDATE statement. could not determine which columns uniquely
identify the rows for "Customers"

'Customers' is the only table from the database that im using for this
query, so it cant be anything to do with a problem of having multiple
tables. and the primary key is set. so i dont understand what the
problem is.

im using asp.net 2003, a microsoft access database, and an
OdbcDataAdapter.

can anyone help?

Apr 11 '06 #1
7 3563
It sounds like the primary key is NOT set, or has duplicate values

Jeff
"bazzer" <so*******@yahoo.com> wrote in message
news:11**********************@z34g2000cwc.googlegr oups.com...
i am having trouble updating a datset because i get the follwing error
in the Data Adapter configuration Wizard:

Generated UPDATE statement. could not determine which columns uniquely
identify the rows for "Customers"

'Customers' is the only table from the database that im using for this
query, so it cant be anything to do with a problem of having multiple
tables. and the primary key is set. so i dont understand what the
problem is.

im using asp.net 2003, a microsoft access database, and an
OdbcDataAdapter.

can anyone help?

Apr 11 '06 #2
ive tried linking to a database with only one table, that has 2 fields,
'numbers', and 'names', set the primary key to numbers, and still it
wont work. ive even tried using windows forms and still i get the same
errors.

Apr 12 '06 #3
Did you check my suggestion?

"bazzer" <so*******@yahoo.com> wrote in message
news:11**********************@i40g2000cwc.googlegr oups.com...
ive tried linking to a database with only one table, that has 2 fields,
'numbers', and 'names', set the primary key to numbers, and still it
wont work. ive even tried using windows forms and still i get the same
errors.

Apr 12 '06 #4
your suggestion? checking if the primary key is set, and checking for
duplicate values?

primary key is definetly set. and its set to Autonumber. By duplicate
values do you mean duplicate fields or primary keys. but as i said, ive
tried linking to a database with only one table, that has only 2
fields, 'numbers', and 'names', set the primary key to numbers, and
still it
wont work even with the most basic table. ive even tried using windows
forms and still i get the same errors. im about ready to give up really
cause no one seems to have a clue whats wrong. myself included. i can
only assume its something to do with the connection to the database
maybe. thanks for the help though. if u think of anything else let me
know.

Apr 12 '06 #5
Weird. Perhaps create a brand new database and try there? Perhaps it's
corrupted?

Jeff

"bazzer" <so*******@yahoo.com> wrote in message
news:11**********************@z34g2000cwc.googlegr oups.com...
your suggestion? checking if the primary key is set, and checking for
duplicate values?

primary key is definetly set. and its set to Autonumber. By duplicate
values do you mean duplicate fields or primary keys. but as i said, ive
tried linking to a database with only one table, that has only 2
fields, 'numbers', and 'names', set the primary key to numbers, and
still it
wont work even with the most basic table. ive even tried using windows
forms and still i get the same errors. im about ready to give up really
cause no one seems to have a clue whats wrong. myself included. i can
only assume its something to do with the connection to the database
maybe. thanks for the help though. if u think of anything else let me
know.

Apr 12 '06 #6
tried that too a few times im afraid.

Apr 12 '06 #7
I did see this from a Google search

If I switch to OleDbConnection instead of OdbcConnection, everything's ok.

"Jeff Dillon" <je********@hotmail.com> wrote in message
news:OP**************@TK2MSFTNGP04.phx.gbl...
Weird. Perhaps create a brand new database and try there? Perhaps it's
corrupted?

Jeff

"bazzer" <so*******@yahoo.com> wrote in message
news:11**********************@z34g2000cwc.googlegr oups.com...
your suggestion? checking if the primary key is set, and checking for
duplicate values?

primary key is definetly set. and its set to Autonumber. By duplicate
values do you mean duplicate fields or primary keys. but as i said, ive
tried linking to a database with only one table, that has only 2
fields, 'numbers', and 'names', set the primary key to numbers, and
still it
wont work even with the most basic table. ive even tried using windows
forms and still i get the same errors. im about ready to give up really
cause no one seems to have a clue whats wrong. myself included. i can
only assume its something to do with the connection to the database
maybe. thanks for the help though. if u think of anything else let me
know.


Apr 12 '06 #8

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

5 posts views Thread by Nick Stansbury | last post: by
6 posts views Thread by Robert Schuldenfrei | last post: by
9 posts views Thread by Hasan O. Zavalsiz | last post: by
9 posts views Thread by HAN(removethis)twister | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.