|
Not automatically. A date field has to hold a valid date at all times. There is the possibility to ALWNUL in the DDS and this leads to - just another indicator in your RPG program. This indicator appears in the disguise of %NULLIND(fieldname). But even then the date field holds a valid date, just the null indicator is on. ----- Original Message ----- From: "Rob Berendt" <rob@dekko.com> To: <RPG400-L@midrange.com> Sent: Wednesday, January 19, 2000 7:51 PM Subject: RE: Date Field Printing > I question 'the absence of a date is stored as 0001-01-01'. Isn't > it stored as *null instead? Does *null print this way? Or is this > the effort of picking some arbitrary date to indicate the lack thereof? > > > > > > JFritz@sharperimage.com on 01/19/2000 01:43:44 PM > Please respond to RPG400-L@midrange.com@Internet > To: RPG400-L@midrange.com@Internet > cc: > Fax to: > Subject: RE: Date Field Printing > > I don't know if this is better, but it doesn't use indicators. > > Print a character field large enough to hold the date with separators. If > the date is *loval, make the output field blank, otherwise move the date > into it. You could do something similar with a numeric field and the Y edit > code. > > > -----Original Message----- > > From: Joe Giusto [mailto:JGiusto@patuxent.com] > > Sent: Wednesday, January 19, 2000 9:37 AM > > To: 'RPG400-L@midrange.com' > > Subject: Date Field Printing > > > > > > /* SNIP */ > > > Now the absence of a date is stored as 0001-01-01 and that's > > what prints in > > place of what used to be nothing (or blank). It is confusing > > to the users > > and every time someone new sees it we have to explain it again. > > > > I have begun testing date fields to be printed and using > > indicators (yuck) > > to condition the field to print or not print. > > > > There's got to be a better way. Any suggestions would be appreciated. > > > > Thank you, > > > > > > Joe Giusto II > > Patuxent Publishing Company > > > +--- > | This is the RPG/400 Mailing List! > | To submit a new message, send your mail to RPG400-L@midrange.com. > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- > > > +--- > | This is the RPG/400 Mailing List! > | To submit a new message, send your mail to RPG400-L@midrange.com. > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.