RE: Unusual date / time stamp error when EXFMT is run

["D.W." <dpalme@xxxxxxxxxxx>]

It is, I am going to use the work around of setting the DSPF date fields
to type B and inz them to the current date and let the user change them
as needed.

It will solve the problem for now....thanks everyone for your help and
assistance.


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Marvin Radding
Sent: Tuesday, October 25, 2005 5:37 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Unusual date / time stamp error when EXFMT is run


And I thought the date was formatted to *USA?

Marvin


-----Original Message-----
From: rpg400-l-bounces+mradding=dpi-west.com@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+mradding=dpi-west.com@xxxxxxxxxxxx] On Behalf
Of Michael Jacobsen
Sent: Tuesday, October 25, 2005 2:36 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Unusual date / time stamp error when EXFMT is run

rpg400-l-bounces@xxxxxxxxxxxx wrote on 10/25/2005 04:22:51 PM:

> Eval a date field to *LOVAL does not work. It has to be a valid date 
> which *loval is not.  Make it a valid date as in
> 
> D #loval    s      d     inz(d:'0001-01-01')

I haven't been following this thread, but isn't *LOVAL = '0001-01-01' ?
I 
was under the impression that *LOVAL is the lowest *valid* value of 
whatever the field is defined as?


Michael Jacobsen
System Programmer, IT
First Financial Bank, NA
(812)  238-6319

> 
> Unless you have defined a date format such as *USA for the display
field
> then you have to use this:
> 
> D #loval     s    d   inz(d:'1940-01-01')
> 
> Marvin