×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Scott
using 8 digits causes real estate concerns to be addressed. Most folks can figure out the real meaning of display. Same for reports. I do not thinks date reformatting is a Compliance issue for display and printing purposes... but more an incomplete implementation/design. I cannot think of any reason reformat for 8 digits to 6 has to be dependent upon century or a windowing schema.
I do agree with you on the use of 8 digits to be Y2K Compliant in an ideal world. Lack of the full 8 will lead to multiple second comings of Y2K many times as those that used this method approach the window limits un expectedly, But that is another matter.
At 10:31 AM 02/08/2000 -0600, you wrote:
>Why not change the screen to show the FULL date? NO chance of confusion
>then. No extra coding involved except a simple move and doing the change
>to the DSPF. If you don't have the space to add the 2 characters, then
>you probably have an over busy screen that should be simplified.
>
>To me the date window is not a Y2K solution, it is a band-aid until the
>real solution can be done. It pains me to see people who show a 6 digit
>date and say they are Y2K compliant. It is a real bugger trying to enter a
>date that you want to be 12/31/9999 and the program takes it as 12/31/1999.
>Then you have to figure out why everything is expiring when it should not
>be.
>
>My two cents,
> Scott
>
>boothm@earth.Goddard.edu wrote:
>>
>> I think what irritates me most though is that we can not use the new
>> solution to move an 8-digit date to a 6-digit date outside the 40-39
>> window. Users understand birthdays. If they see a birthday of 3/31/22 on
>> their screen they know it isn't 2022. I have to go back and check stuff
>> but for the moment it looks to me like I will be moving the 8-digit date
>> to a 6-digit date first. What I am after is the 8-character field with
>> "/"s in place, or if the date is blank, no "/"s.
>>
>> _______________________
>> Booth Martin
>> boothm@earth.goddard.edu
>> http://www.spy.net/~booth
>> _______________________
>>
>+---
>| 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
>+---
>
Glenn
__________________________________
Glenn Ericson,
IBM Certified Specialist
Phoenix Consulting LLC
East Elmhurst, NY USA
Phone 718 898 9805 Fax 718 446 1150
mailto:Glenn-Ericson@att.net
___________________________________ +--- | 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 thread ...
Re: Date fields and moving from yyyymmdd to mmddyy, (continued)
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.