FIX: SQLGetData Fails on Multiple Active Statement Handles

Last reviewed: April 8, 1997
Article ID: Q153836
The information in this article applies to:
  • Microsoft SQL Server version 6.5

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.


Additional query words: SQLGetData active statements
Keywords : SSrvProg
Version : 6.5
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.