BUG: Fully Qualified Table Names Causes dbcursoropen() to HangLast reviewed: April 29, 1997Article ID: Q116048 |
The information in this article applies to:
- Microsoft SQL Server Programmer's Toolkit, version 4.2BUG# 10041 (4.21)
SYMPTOMSA call to dbcursoropen() with a SELECT statement where the table name is fully qualified in the FROM clause can result in DB-Library going into an infinite loop. This results in the application repeatedly submitting "use <database name>" against SQL Server within the dbcursoropen() function.
WORKAROUNDThe problem will not occur if dbuse() is called before the dbcursoropen() call and the table name in the FROM clause of the SELECT statement is not fully qualified.
STATUSMicrosoft has confirmed this to be a problem in DB-Library version 4.21. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
|
Additional query words: dblib
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |