|
I have to disagree here. The 28 year fix is a perfectly viable fix. Maybe It's not the prettiest or best solution but you have to remember that the way the computer actually stores the date doesn't look anything like the date in the first place. Many internal date formats are based on an arbitrary year anyway. DOS-1980, Delphi 1899, VMS-1858, AS400 - 0001 (A year which never even existed) The computer translates it for us. This solution just moves the translation from the database to the application. If you create just two conversion/formatting routines for these dates and use them in all of your user interface applications then it should work. Am I using it - no! But it is not the end of the world either. > > > >I would plan on leaving a company that made that choice. There are many > > >other solutions that would also work and be more strait forward. > +--- | 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.