Re: Specifying dates in DDS

neil.williams@pocruises.com wrote:

>      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 ?

I prefer storing the date as CCYYMMDD.  This can be easily moved into *USA
(MM/DD/CCYY) *EUR (DD.MM.CCYY)date fields for display/print.  However, if you 
use
Query or SQL a lot, then date conversion within is cumbersome (can be done).
Also, this will also allow you the special all 0 or all 9 date approach.  Best 
of
all, you still have your old date as part of your new date!  You can easily 
write
a proc to supply you with various forms of dates for display/print.
--
Thank You.

Regards

Dave Mahadevan.. mailto:mahadevan@fuse.net


+---
| 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
+---