OleDbdataAdapter>> Could not determine which columns uniquely identify the rows for ...
-
hi i just want to configure my adapter such that i can update information to Access db. but i got this error from the OleDbdataAdapter>> Could not determine which columns uniquely identify the rows for.... i already spent the past few hours finding online solutions but to no avail, mainly because the forum dicussions stopped halfway and the language is not the same as mine. just to check with you: since i can already get the selected data out from db using parameterized query, does that mean that if i can update successfully, my updates will return to the EXACT table fields it came from? please, please help me to get this part going.... it's urgent! i really appreciate any help! thanks in advance! -- modified at 5:20 Monday 29th August, 2005
-
hi i just want to configure my adapter such that i can update information to Access db. but i got this error from the OleDbdataAdapter>> Could not determine which columns uniquely identify the rows for.... i already spent the past few hours finding online solutions but to no avail, mainly because the forum dicussions stopped halfway and the language is not the same as mine. just to check with you: since i can already get the selected data out from db using parameterized query, does that mean that if i can update successfully, my updates will return to the EXACT table fields it came from? please, please help me to get this part going.... it's urgent! i really appreciate any help! thanks in advance! -- modified at 5:20 Monday 29th August, 2005
-
Do you fetch the primary key from the table? Do you have a primary key? --- b { font-weight: normal; }
oh yes, i forgot to mention about the error i got in Access. i've a field named IDno and this field is added to each and every of my tables. is it ok or correct to let all tables have IDno as pk? i thought it's ok so i tried.. i let table1 have IDno as pk. but then when i tried to let IDno be pk in table2, it gives me error regarding duplicate pk so im stuck now... if i dont use IDno, i donno what is best used as primary key in table2 and the rest of my tables. there's a button on the toolbar called Index Name, so i typed "PrimaryKey" and selected "IDno", hoping that through this way, perhaps table2 can have IDno as pk. does this way make IDno a pk? i doubt so.. i doubt so because if IDno is made to be a pk in my table now, how come i still get the same error as before i tried typing "PrimaryKey" and selecting "IDno" in Index Name? the error is: Could not determine which columns uniquely identify the rows for "table2". for table1, things are fine, i used OleDbAdapter and generated all the statements successfully. but doing this table2 gives me error, i just want to use OleDbAdapter to build update and delete functions too. i donno why it failed. it succeeded in generating Select and Insert statements... so what's wrong? i really have no idea what's wrong. please help. i really need some guidance. thanks! -- modified at 3:08 Tuesday 30th August, 2005