This issue is known to occur only when using ODBC drivers for MS SQL Server. It occurs because the SQL Server / ODBC drivers for SQL Server do not allow operations on a cursor if the result set of a previous cursor was fetched prior to the end of the result set, i.e. if a SELECT is made on cursor c1 and not fetched until the end of the result set, then another SELECT on cursor c1 is not possible until cursor c1 is closed. This problem only occurs with ODBC for SQL Server, and only if at the time of replay there are more rows than during the record. Manually changing the second parameter to SQL_FETCH_ALL should resolve this problem e.g.: OdbcFetch(c1, SQL_FETCH_ALL , 1, SQL_FETCH_NEXT); // 2 rows fetched Old KB# 18389
↧