FIX: SQLGetData Fails on Multiple Active Statement Handles (153836)
The information in this article applies to:
This article was previously published under Q153836 SYMPTOMS
When there are two active statement handles, SQLGetData fails to
fetch results from the two statement handles simultaneously.
The following error is generated:
szErrorMsg="[Microsoft][ODBC SQL Server Driver]Connection is busy
with results for another hstmt"
WORKAROUND
Bind the result set columns using SQLBindCol before a fetch. This allows
multiple active statement handles .
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server
version 6.5. This problem has been corrected in U.S. Service Pack 1 for
Microsoft SQL Server version 6.5. For more information, contact your
primary support provider.
MORE INFORMATION
When you are using server-based cursors, the connection between the client
and server does not remain busy between operations. This allows you to have
multiple cursors statements active at the same time. However, with the SQL
Server ODBC driver 2.65.0121v, an attempt to fetch data using SQLGetData
between multiple statement handles fails. If SQLFetch is being done on a
statement handle hstmt1 and if, before a result of SQL_NO_DATA_FOUND is
returned, another statement hstmt2 is allocated and another fetch operation
is done, and then a simultaneous SQLGetData is done on hstmt1, the result
will be a "Connection is busy with results" error.
| Modification Type: | Major | Last Reviewed: | 10/3/2003 |
|---|
| Keywords: | kbfix KB153836 |
|---|
|