BUG: SELECT with CASE Can Cause Parser Error 403

Last reviewed: December 8, 1997
Article ID: Q151681

6.00 WINDOWS kbprg pbprb kbbug6.00

The information in this article applies to:

Microsoft SQL Server, version 6.0

SYMPTOMS

A SELECT statement against multiple tables that includes a CASE expression can result in parser error 403:

   Invalid operator for datatype op: UNKNOWN TOKEN type: char

To reproduce this problem, the tables should have at least two columns of datatype CHAR, and three tables must be involved in the SELECT statement. Also, a join must be specified between two of these tables.

WORKAROUND

Avoid using the CASE expression by rewriting the query using the IF..ELSE conditional Transact-SQL statement.

STATUS

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

Additional reference words: 6.00
KBCategory: kbprg pbprb kbbug6.00
KBSubcategory: SSrvProg
Keywords : SSrvProg kbbuglist
Version : 6.00
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: December 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.