Vb6 row cannot be located for updating
When using the ad Use Server server-side cursorlocation, responsibility for handling the data generated by a query lies with the database server.My SQL itself does not support server-side cursors, so the data handling is actually done by the Connector / ODBC driver.Client-side cursors, specified with the ad Use Client keyword, are handled internally by ADO.These cursors offer more functionality than their server-side counterparts, and also result in less load being placed on the server.The client may communicate with the server to send changes back to the server.This makes the static cursor more resource-intensive for the client and less resource-intensive for the server, as the result set is stored in the client's memory instead of the server's.In addition to the two cursor locations, there are four cursor types, three of which are supported under Connector/ODBC: as your cursor location.With a static cursor, the server will send the result set to the client, after which there will be no further communication from the server to the client.
This allows your server to scale a lot better than with server-side cursors.
If a different client makes changes to the underlying data after the query results are sent, the original client will receive no notification of the change.
A static cursor is bi-directional, meaning that your application can move forwards and backwards through the recordset.
The purpose of this article is to assist the Visual Basic developer in choosing the proper cursor location, cursor type, and lock type to use when programming Visual Basic (or VB) applications that use My SQL as a back-end database through ADO and Connector/ODBC (My ODBC).
This article will assume that the reader is using the My SQL RDBMS, but should apply to developers using other database management systems.