Microsoft KB Archive/105326

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 08:45, 20 July 2020 by X010 (talk | contribs) (Text replacement - """ to """)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)



BUG: ESQL: Null Indicators May Not Work with Datetime Columns

Last reviewed: May 5, 1997
Article ID: Q105326

The information in this article applies to:

  • Microsoft Embedded SQL version 4.21 for COBOL

BUG# 9445 (4.21)

SYMPTOMS

In Embedded SQL (ESQL) for COBOL, a static INSERT statement does not insert NULLs into a datetime column, even if the NULL indicator is set. When inserting into a datetime column, the NULL indicator is simply ignored, and the following default datetime value is inserted:

   1/1/1900 12:00AM

However, if the INSERT statement is dynamic, NULLs are inserted correctly using null indicators.

CAUSE

SQL Server Embedded SQL for COBOL incorrectly ignores null indicator when inserting NULLs into a datetime column if the insert is static.

WORKAROUND

Use dynamic SQL statements, or perform updates on the datetime column to change the default datetime values to NULLs using an insert trigger.

STATUS

Microsoft has confirmed this to be a problem in Embedded SQL version 4.21 for COBOL. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.



Additional query words:

Keywords : kbbug4.20a kbbug4.21 kbprg SSrvProg
Version : 4.21 | 4.21
Platform : MS-DOS OS/2


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