BUG: NSQLPREP Substitutes DBCS Object Name with a Null String

• Microsoft Embedded SQL for C Programmer's Toolkit, version 6.5

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:

1. Create a table with a DBCS name.
   

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




2. 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 */ 
         }
      




3. 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          : kbprg kbusage SSrvESQL_C SSrvProg kbbug6.50 
Version           : 6.5
Platform          : WINDOWS 
Issue type        : kbbug 

Last Reviewed: April 9, 1999