BUG: Fully Qualified Table Names Causes dbcursoropen() to Hang

Last reviewed: April 29, 1997
Article ID: Q116048

The information in this article applies to:

  - Microsoft SQL Server Programmer's Toolkit, version 4.2

BUG# 10041 (4.21)

SYMPTOMS

A 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.

WORKAROUND

The 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.

STATUS

Microsoft 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
Keywords : kbbug4.21 kbprg SSrvDB_Lib SSrvProg
Version : 4.21 | 4.21
Platform : OS/2 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 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.