Re: Year 2000 Recommendations?
Date: 1996/04/16
Message-ID: <4l1auu$n47_at_gossamer.itmel.bhp.com.au>#1/1
In article <4l0385$ml9_at_ussun2n.glaxo.com>, John Jones <jmj22026_at_us1j69.glaxo.com> says:
>
> Just ran across the same problem the other day. We are using PowerBuilder as a
>frontend. We have to pass the date from PB in characters and then reconvert in a
>stored procs once it gets to Oracle. All you have to do is use the MM/DD/RR date
>format. Notice the "RR" instead of "YY". Oracle says if the year is 51 or greater
>then it is 1900, and if it is 50 or less then it is 2000. This works great unless
>the field you are working on is a birthday and you have people born before 1950.
>Anybody got any ideas how to handle this????
>
>
>
>
>John Jones
>Oracle Consultant
>jmj22026_at_us1j69.glaxo.com
>My views are my own, no matter where they originate
>
Dead easy - if you are using this large a range of years, then you MUST
use 4-digit years.
My grandmother was born in 1899 (yes, she's still with us). Pretty soon
any system which has to handle people-type data will have people born
after 2000 - and the way my grandmother is heading, she's going to make it.
So we have to be able to handle dates from 18.. to 20..
4-digit years is the only way to go. This is the only way (that I
know of) that you can handle data if this sort of data is within
your systems specs.
A lot of systems, eg order-entry (I was tempted to say most, but
I'd probably just get get flamed) only use fairly 'current' dates,
so a combination of 2-digit years and RR format is satisfactory
HIH
Lee
Lee Levy, ISSD Technical Dream Team, Del Code (34) BHP Information Technology, ACN 006 476 213 PO Box 261, Warrawong, NSW 2502, Australia PH: +61 42 75-5485 Fax: -5500 Tie: 8855- Internet : levy.lee.ls_at_bhp.com.au
Opinions expressed are mostly my own, so give me some credit. Received on Tue Apr 16 1996 - 00:00:00 CEST