Row cannot be located for updating vb6 access

I am using ad Open Key Set, why doesn't it give an error if theonly one I will get is ad Open Static ? I have changed the query to explicitly naming the columns in theselect clause. With aduse Client, the onlycursor type you will get is static (ad Open Static)Your decision as to cursor type depends on your need for functionality.I open the recordset just to change several column values (and nothingelse), then I do the . If I open the connection using ad Use Client, can I just for this recordsetuse server side cursor ? The "Programming ADO" book talks about clientside cursor, I usead Use Client cursor Location for the connection, and I did notset/change the cursor location for the recordset. It is really up to you which type you need since i don't know therequirements of your application.I am using ad Open Key Set, why doesn't it give an error ifthe only one I will get is ad Open Static ?Use the Cursor Type property to specify the type of cursor that should beused when opening the Recordset object.These issues are ones you would need tohandle yourself if you resorted to a stored procedure.

row cannot be located for updating vb6 access-25row cannot be located for updating vb6 access-57row cannot be located for updating vb6 access-27row cannot be located for updating vb6 access-35

These issues are ones you would need tohandle yourself if you resorted to a stored procedure. I am not clear how I should handle concurrency issues if I call a storedprocedure to do the update. You should make a point ofexplicitly naming the columns in your select clause so that1) you only retrieve the data you need, and2) you don't force ADO to generate metadata, which sometimes requires anextra trip to the database??? particularly the first chapter(chapter 11, I think)Here is the link again. If your would be my preference, except that you must have had some reasonto choose an expensive keyset cursor ...You will get aquicker response by posting to the newsgroup.With aduse Client, the only cursor type you will get is static(ad Open Static)on the other hand if you are keeping a recordset open for any length oftime,requiring you to worry about what other users are doing, then you need aserver side cursor, either keyset or dynamic.You will get aquicker response by posting to the newsgroup. I have changed the query to explicitly naming the columns in the selectclause. The error that I got is causeed because in between executing the query"select [Order], Status, Price, Location from my Table where [order] = '" &(s Order) & "' and calling the .The "Programming ADO" book talks about clientside cursor, I use ad Use Clientcursor Location for the connection, and I did not set/change the cursorlocation for the recordset. Update method somebody else already updateeither Status, Price,or Location column. If I understand it correctly, does it mean that I can trap this error andthen resubmit the same query and then do update again ?

Leave a Reply