|
ok....Bob said: "Because the RPG IV converts the date from the display file into *ISO within the program. " Which my statement was referring to, IF the date field is defined on the DSPF as *MDY, then the RPG compiler SHOULD always be *MDY for this date field. NOT *ISO here & *MDY there... just my 2 coppers worth... Thanks, Tommy Holden -----Original Message----- From: Buck Calabro [mailto:buck.calabro@xxxxxxxxxxxx] Sent: Friday, January 28, 2005 12:13 PM To: rpg400-l@xxxxxxxxxxxx Subject: Re: Why RPG IV Sucks > sounds reasonable that if the date field is > defined with a date format that the RPG > compiler SHOULD keep the date format... Something like keeping all dates as a secret internal format of *ISO and when other formats are used, down translate the internal date to the display date? But how would you handle incoming dates, e.g. 07/27/01 This could be my grandfather's date of birth, or my 2 year old's. Which *ISO date would you choose to promote this *MDY date to? Remember that the very next record typed in may require the _other_ century interpretation, so a fixed window doesn't cut it. --buck -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.