Arlene M Soderlund wrote:
>This causes me to wonder, how many of us are out there creating a new date
>problem in our applications? For example, have you created any printer files
>or display files with a *MDY output field? If so, did you realize that these
>are likely to fail on Jan 1st, 2040.
>Will I care in 40 years when I am at retirement age and my code is beyond it
>useful lifespan, hmmmm sounds just like those guys who started the two digit
>date thing. <grin!> I see no effect on my business now! Actually I would hope
>in 10 or 20 years they can change it to slowly forward and that the year 40
>cutoff would no longer be necessary.
Really sounds like a logic problem GT,or LT Vs GE or LE. I've uncovered this type mistake before during some IV & V audits, in other areas.
The true problem is century transition. Once you are beyond "00" and the period your company has to look back in time there is no longer any reason for a four digit year until 2098/99 again.
That says you could go back to your original code when this happens.
One of the easy ways to do this is via the Encapsulation methods offered by MS4. The I/O for internal files in the DB is trapped to operate in 19xx time frame and the DB is backdated -28 years. This is different then some other methods,in that, within a few hours the entire encapsulation can be removed form both programs and the DB and all is back to pre-encapsulated changes. your original tried & true code is back for the balance of the century , if you wish.
+--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.