PRB: Limitations of ADO Client Cursor and Data-Bound Controls with DB2OLEDB (269597)

MORE INFORMATION

This behavior is observed only with the DB2OLEDB provider that is included with SNA 4.0 Service Pack 3 (SP3) and later. (This change was made after the SNA 4.0 SP2 provider shipped to fix other problems and improve performance.) This problem does not affect DB2/400 or other supported platforms.

The OLE DB Provider for DB2 that is included with SNA Server 4.0 SP3 and later supports updating capabilities when used with a client cursor engine. To support updates (UPDATE, INSERT, and DELETE) using a client cursor engine, the values in at least one column in the target table must be unique, and the Auto Commit Mode parameter must be set to False when configuring the data source, or when this parameter is passed as part of a connection string.

Earlier versions of the OLE DB Provider for DB2 do not support any updating capabilities when used with a client cursor engine. In other words, if the client cursor engine is enabled using Remote Data Service (RDS) or ADO, the SNA 4.0 SP2 OLE DB Provider for DB2 cannot be used to update data on the host. The ADO recordset is treated as if it were read-only.

Microsoft Visual Studio 6.0 offers a number of ADO data-bound controls, including a data grid and the ADO Data Control. When using these ADO data controls, you must set the CursorLocation property on the recordset to adUseClient. Also, when using these ADO data controls with DB2 for OS/390, you must set the OLE DB Provider for DB2 Auto Commit Mode property in the data link or connection string to False. When using the client cursor engine with DB2 for OS/390, you must set the OLE DB Provider for DB2 Auto Commit Mode property in the data link or connection string to False. This is not required when connecting to DB2 for OS/400.