Re: Oracle 7.3 and Year 2000

The reason for this behaviour is the YYYY format, if you enter a date in dd-mon-yy format and the database format receiving this date is yyyy it automatically puts the ACTUAL century in the leading 2 yyyy digits.

This could cause some problems during the cenrury transition period.

You have two solutions :

1. You force date entry in 4 digits and set your input mask to the same YYYY as the database format. In this case you can not allow input in yy format.
2. You use the RR format wich does a century calculation.I don't know the exact algoritm but it's something like YY >50 => Actual century YY<50 next century. I consider this to be a workaround . It's a solution that probably will work fine for 20 to 30 years.

Merlin Team heeft geschreven in bericht <774i0l$fr1$1_at_news1.cableinet.co.uk>...
>Hi,
>
>I have encountered a problem whilst attempting to enter dates in the format
>dd-mon-yy into my database.
>
>The database server was configured using the default settings i.e American
>language set. When I query nls_parameters the date format is shown as
>dd-mon-yy.
>
>Using sql*loader I insert the data into a date field and it appears to
>display fine. If I use the alter session command to set the
nls_date_format
>to dd-mon-yyyy any dates that have the year set as 00 or greater display as
>1900, 1901 etc.
>
>Can anybody suggest what I need to do to get the data accepted as 2000,
2001
>etc. Ideal the solution should be set in the initialisation file.
>
>Thanks
>
>Paul
>paul_merlin_at_hotmail.com
>
>
Received on Sun Jan 17 1999 - 03:52:03 CST