RELEASE NOTES for INFORMIX-ESQL/C for Windows 5.01.Wh1
              ====================================
                        RELEASE NOTES
                            FOR
              INFORMIX-ESQL/C for Windows 5.01.WH1
                        As Of 12/19/95
              ====================================


TABLE OF CONTENTS

I.      BUGS FIXED WITH 5.01.WH1

II. ERROR MESSAGES

III. MEMORY LEAK FIX

IV. KNOWN PRODUCT DEFICIENCIES


I. BUGS FIXED WITH 5.01.WH1 Bug 42552: ESQLMF.EXE does not get spawned by ESQL.EXE to perform multibyte charachters to single byte translation. Problem: User had to invoke ESQLMF.EXE explicitely on .c file. Solution: Fixed ESQL.EXE to invoke ESQLMF.EXE after preprocess (ESQLC.EXE) and before compile (CL.EXE) phase. Bug 43309: Default locale should be en_us.1252 in place of en_us.8859-1. Problem: When user does not specify Client locale, it was defaulted to en_us.8859-1. Solution: Default locale is changed to en_us.1252. Bug 43367: Error message 32766 (Unknown error message number XXX), where XXX is the error number, prints wrong error number for error number 32767. Problem: Integer type (2 bytes) was used instead of Long type (4 bytes). Solution: Changed to Long type.
II. ERROR MESSAGES The New Error Messages as listed in Release Notes for version 5.01.WG1 are updated. Some more error messages are added for Multibyte related error messages generated by ESQLC.EXE and ESQLMF.EXE. Online help on these Error Messages is provided by FINDERR.EXE utility. III. MEMORY LEAK FIX ESQL/C did not free all the memory allocated for the cursors. Cursor memory leak is caused due to memory and execution time related optimizations. The major constraint while fixing memory leaks was backward compatability. Most of the memory leak fix benefits can be enjoyed by existing applications. However to take advantage of all the fixes, you need to recompile your application with the latest ESQL/C product. If your application uses lot of cursors only for short duration of times, it is recommended that you recompile your application. You need to use new ESQL/C flag -ecd (enable cursor deletion). For more details, refer to ESQL/C Documentation Notes.
IV. KNOWN PRODUCT DEFICIENCIES rdefmtdate(&D,"MM-DD-YYYYC1","06-17-0060") returns -1263. Returns correct if "06/17/0060" used. (bug 43574) Abbrievated Chinese/Tiwanese Ming Guo Era is '-' (hyphen). Year component in date 06-17-0060 is ambiguous and hence the problem. If you are using Chinese/Tiwanese locale, do not use '-' (hyphen) as separator for date representation. C runtime library function printf() behaves unpredictable if the client locale uses '%' character as part of multi-byte characters and string containing such multi-byte characters is passed to the printf() function. (bug 43102) Requires multi-byte aware C compiler. Microsoft and Borland do not have (Unicode only) multi-byte aware C Compilers. Inconsistent handling of partial characters when using Put Cursor. (bug 44302) Example: You have an 8 byte CHAR column. You issue a Put Cursor command to insert string "ABC