Current recordset does not support updating adodb

On the Visual Basic side, I recommend you have service pack 5 installed for VB, which you can download here. In ADO, when we talk about cursors, we are essentially talking about a set of rows.

Additionally, the latest version of MDAC (Microsoft Data Access Components) should be installed, and can be found here (currently 2.7 SP1). When you execute a query that returns rows of data, such as .

The most efficient way to access data for display to the screen out output to a file is to use a lock type when opening a recordset.

This combination is often referred to as a Firehose Cursor.

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.

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.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.Recordset objects can also explicitly set a cursorlocation different than the connection objects cursorlocation as long as it is set before the recordset is open.The two options available for this property are being the default property.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.