BUG: Syntax Error on SQLNumResultCols on GROUP BY in Subquery

Last reviewed: April 8, 1997
Article ID: Q153852

The information in this article applies to:

Microsoft SQL Server versions 6.0 and 6.5

SYMPTOMS

If an ODBC application does a SQLNumResultCols() after a SQLPrepare() of a query containing a GROUP BY in a subquery, but before having issued SQLExecute(), the Microsoft SQL Server ODBC Driver will issue an error:

   szSqlState = "37000", *pfNativeError = 107, *pcbErrorMsg = 134
   szErrorMsg="[Microsoft][ODBC SQL Server Driver][SQL Server]
              The column prefix 'B' does not match with a table
              name or alias name used in the query."

WORKAROUND

Do not issue the SQLNumResultCols() call until after issuing the call to SQLExecute().

STATUS

Microsoft has confirmed this to be a problem in the Microsoft SQL Server ODBC Driver version 2.50.0121. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: SQLBindCol SQLSetPos
Keywords : kbbug6.00 kbbug6.50
Version : 6.0 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.