.PN1
L....................................................................A
.FO2
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA>@@
[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[
L....T..T...................................R...L....................A
UNOTE 006‰                                                 Page # of 1

                                                      Ref:  UNOTE 006~
From‰:‰ Customer Services                                 16 Dec 1988~
L....T..T............................................................R
Re‰  :‰ Bug in handling DD/MM/YY date format in both USQL and UFORM
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA>@@
[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[
L.......T.......T.......T.......T.......T.......T.......T.......T....R

Please find below a bug description and work around that is too
lengthy to be covered adequately in the the SSR.

Problem synopsis:@@
CCCCCCCCCCCCCCCC 

"Invalid year in date" and "Reply not a valid date" when trying to@@
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
input date fields in database forms when DBDATE variable set for USQL@@
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
to understand DD/MM/YY date format.@@
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA 

In order to switch Uniplex to "European" date format, the DATEFMT flag
in uniplex.sys (uniplex.cmd in version 5) must be set as:@@
   IIIIIIIIIII  IIIIIIIIIII                              

DATEFMT='DD/MM/YY'@@
AAAAAAAAAAAAAAAAAA

This affects all database interaction (forms and USQL reporting), but
will not affect USQL data entry.

eg:  You will still get "Invalid month in date" from USQL when@@
                         AAAAAAAAAAAAAAAAAAAAA                
entering something like:  insert into mytab values ('14/07/87', ...)~@@
                          AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA 

To make USQL accept this format date in data, you must set the
INFORMIX defined environment variable DBDATE.

eg:  DBDATE=DMY2/ export DBDATE;  uniplex@@
     AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

However, if you just do this, you will find that Uniplex database
forms no longer accept dates at all - producing one of the two error
messages shown above.

This bug exists in both version 5 and version 6 (6.01) of Uniplex.

Work around:@@
CCCCCCCCCCC 

The work-around is to set DBDATE only for USQL, and not for UFORM.
This can be easily be done in one of 2 ways:

H....L..T.......T.......T.......T.......T.......T.......T.......T....R
 i)  Amend all menu and softkey calls to USQL

     eg: From:  4 ! usql,,,C~@@
                AAAAAAAAAAAA 
           to:  4 * 'DBDATE=DMY2/ usql',,,C~@@
                AAAAAAAAAAAAAAAAAAAAAAAAAAA 
     and from:  3=X(,,,IOR,exec usql,106)~@@
                AAAAAAAAAAAAAAAAAAAAAAAAA 
           to:  3=X(,,,IOR,DBDATE=DMY2/;export DBDATE;exec usql,106)~@@
                AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA 

ii)  Rename the USQL program and then write a small pre-processor
     shell script called usql.@@
                         IIII 

eg:  cd UAP/bin~@@
     AAAAAAAAAA 
     mv usql usql.real~@@
    AAAAAAAAAAAAAAAAAA 
     echo '~@@
    AAAAAAA 
     DBDATE=DMY2/;  export DBDATE; exec usql.real $*' >usql~@@
    AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA 
     chmod 555 usql~@@
     AAAAAAAAAAAAAA 

L.......T.......T.......T.......T.......T.......T.......T.......T....R

Update (July 1989)~@@
CCCCCCCCCCCCCCCCCC 
.SP0.5

.SP1
This bug has been fixed in Uniplex version 6.10. Note, however, that
the Oracle database supports only a single date format.