RE: Next SQL question

The 0001-01-01 would only work for a date in *ISO format.  If a date is in *YMD 
or *MDY format the *LOVAL is different, trying to
remember the window... 1930 to 2029?  So you would either have to use the date 
of 1930-01-01 which would be used as 01/01/30 in SQL
which I believe uses *MDY format.

Of course, I don't' use SQL that much yet at all, but I think I understand most 
of the date issues.

HTH

Regards,

Jim Langston
Programmer/Analyst
Cels Enterprises, Inc.

-----Original Message-----
From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On
Behalf Of Hatzenbeler, Tim
Sent: Tuesday, August 21, 2001 2:09 PM
To: 'rpg400-l@midrange.com'
Subject: Next SQL question

[ Picked text/plain from multipart/alternative ]
My embedded sql/rpg program works, sorta, it works only if my date fields
have real values in them, and not the default 0001-01-01 values...

what should I do?  I keep getting a 183 error, which is a timestamp problem,
but If I force in a date, it does work...  But I was hoping to use *loval to
inform me that my date field is unchanged...

thanks, tim