BUG: NSQLPREP Substitutes DBCS Object Name with a Null String

Last reviewed: April 15, 1997
Article ID: Q166202

The information in this article applies to:

Microsoft Embedded SQL for C Programmer's Toolkit version 6.5

BUG #: 16754

SYMPTOMS

The NSQLPREP substitutes a double-byte character set (DBCS) string with a null string if a DBCS string was used for the object name.

WORKAROUND

To work around this problem, use the single-byte character set (SBCS) for the object name.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Embedded SQL for C Programmer's Toolkit version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The following procedure demonstrates this problem:

Create a table with a DBCS name.

      CREATE TABLE tableName (col INT)
      GO
      /* where tableName must be in DBCS */

Create a <File name>.sqc file that contains the following:

      EXEC SQL INCLUDE SQLCA;
      main()
      {
         EXEC SQL INSERT tableName VALUES (1);
         /* where tableName must be in DBCS */
      }

Run the pre-compiler to generate the <File name>.C file. You will observe the following problem:

      main()
      {
         .....
         /*
         EXEC SQL INSERT tableName VALUES (1)
         */
         .....
         sqlxcall(24, 1, 0, 0, 21, (char far *) "  INSERT  VALUES (1)");
         .....
      }

Additional query words: JIS Wansung Johab Hangul KB BIG-5 Chinese Japanese
Korean
Keywords : kbbug6.50 kbprg kbusage ssrvesql_c SSrvProg
Version : 6.5
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbpending

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 15, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.