|
Hi, Rick: >Is my program non-compliant (or not Year 2000 ready) when I display a date >on screen as DD/MM/YY now or after the year 2000 has arrived? IMO, that information *should* be limited to what you show (or even DD/MM, if applicable) as you have indicated. Some people go way too far overboard on that issue (again, my opinion), and I think a balance is good. If the user is looking at the manufacture date for a certain type of computer, for example, and they see 25/12/04, there will be NO question as to what century that is talking about. Or if they're looking at the expiration date of a credit card, there should be no question what that same date means. Certain things have very short lives (warranties, another fine example). For anything that cannot possibly be considered confusing, I say clean up the screen or report, and give the users other, useful information. Just my $.02. Dennis -- Dennis Lovelady Simpsonville, SC mail: dennis@lovelady.com URL: http://lovelady.piedmont.net ICQ: 5734860 -- "When a man retires and time is no longer a matter of urgent importance, his colleagues generally present him with a watch." - R.C. Sherriff +--- | 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: 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.