|
Thanks to everyone who replied to my question about Pros and Cons of specifying dates as a date field as opposed to 4 chunks of 2 (cc yy mm dd) The arguments for and against each method seem to balance out as a general concept,but I'd just like to try and narrow down the argument a little. What if; 1) The database is accessible stateside and in Europe, and each location wants the dates displayed as 'native' e.g. MMDDYY stateside and DDMMYY in Europe. 2) There are special dates in the RPG part of the application (e.g. 99/99/99 and 00/00/00. 3) We want to write 'Date Engines' for all our date handling/validation, and these must comply with 1) above. Which way are we going to come down now ? Neil H-W _______________________________________________________________ Please note that the e-mail address for P&O Cruises has changed to @pocruises.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@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.