Row cannot be located for updating ado
It contains a primary key that points to an autoinc-Field and several other fields, some of them have default-values defined.
Problem 1) The default-Values are not appearing in the grid, when a new record is added (using the cursor down arrow) I remember this worked in MDAC 2.1 or something Problem 2) When doing some changes in that table via the grid, I often get the above exception (row cannot be lolcated for update).
You'll be able to ask any tech support questions, or chat with the community and help others.
ado-problem: row cannot be located for update (...) Hi all, Im another person who got the row cannot be located for updating-error of ADO.
(My experience is with VB6, and the Microsoft databases.) Most of the code I have written used so far works but I am getting an error from code that I would expect to work. Update" ***************** Run-time error -2147217864(80040e38): Row cannot be located for updating.
Some values may have been changed since it was last read.
When you use all the infrastructure of things like ADODB or ADO. problems can be much harder to find, you are also buying into a lot of stuff you may not need and it may not work with the database you want to use.
I am in the process of converting a My SQL database application that uses this approach from VB6 to VB. I used VBMy SQLDirect in VB6 and have switched to just using My Sql Data Reader and action queries on the VB. This same app also needs to access SQL Server databases for some of its data.
Borland's ADO components default to using all the field values in the selected record to find the record in the database to update.
For that I can use Sql Data Reader and action queries.
At this level SQL Server and My SQL are very similar and I can write a wrapper class over both of them to hide the different data sources from the rest of the program.
Open "SELECT * " _ & "FROM Taps ", _ Con My SQL, ad Open Keyset, ad Lock Pessimistic int TF = -1 Do While Not rs Taps.
So I have a reason for wanting to iterate through the table. Thanks, John Brown You should try selecting the Return Matching Rows option in the DSN configuration dialog, or specify OPTION=2, as the connection parameter.
Search for row cannot be located for updating ado:
One occurs since first publication in DSN config "Were Matching Rows" is not produced even we say exactly it should be in designed.