Hi,

I have a VB application that uses the DB2 OLEDB provider, and also
MSDataShape->ODBC->DB2 CLI.

A particular module builds a query dynamically to fetch a row from a
table, graps the fields and closes the recordset.
A user-triggered action then calls a stored procedure that updates the
record that was previously retrieved..
10 minutes later, the module is required to retrieve the (now updated)
first record, but when it does it gets the old version. The changes are
in the database, and visible from another computer or another module, or
the same computer if I close the application.

In the time between the triggered action and the second retrieval, the
same module may or may not have retrieved other, different, records from
the same table.

I am definitely closing the recordset after reading from it. I get the
same symptoms regardless of whether the data is fetched on a DB2 OLEDB
connection, or the MSDataShape/ODBC one.

Is this something the DB2 client might be doing to me, or VB?

Thanks,
--Greg