Current recordset does not support updating ado
The benefit of server-side cursors is that we gain access to the dynamic cursor type.
This allows us to see any changes to the data that are made by other users in the data our application is accessing.
For an overview of why My SQL is a good choice for Visual Basic developers, see the Why VB/My SQL article on this site.
Your choice of cursor type and cursor location will affect what you are able to do with the data you retrieve, and how changes made to the data by other users are reflected in your copy of the data. Connection object (the ADO object used to broker all data exchanges between the VB application and the My SQL server) has a property known as property can only be set while the connection is closed, and the property will be inherited by any recordset objects that access their data through the given connection object.Most advanced ADO functionality is designed for use with client-side cursors, and I personally use client-side cursors for all my applications (with one exception). Client-side cursors also help decrease load on our My SQL server, since with a static cursor data is sent to the client and then the server has no further communications with the client.This allows your server to scale a lot better than with server-side cursors.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.