Re: Y2K Problem and Oracle 7.3

Dominique Potter wrote:
>
> Hi,
> Can anyone help with this little problem.
>
> Environment:
> Oracle 7.3, Win95, SQLWindows application.
>
> Constraints: Win95 config cannot change, SQLWindows application cannot
> change.
>
> Problem:
> If a user enters a date for the next century, e.g 2001, the SQLWindows
> application passes back to Oracle the date '1901' (it's a BUG). I need to
> provide a solution that will update ANY dates inserted/updated into Oracle.
> I am not worried about dates prior to 1949, hence I tried to set the
> NLS_DATE_FORMAT to 'DD-MM-RRR' to force Oracle into correcting the century.
> This will work if a user enters a two digit century, but not with four digit
> centuries.
>
> One thought would be to create a 'before insert trigger' on every date field
> in every table. This trigger would read the date columns and correct it if
> the century is incorrect. Problem is I have approx two hundred tables with
> *lots* of date fields.
>
> Does anyone have any thoughts on this ? Any help would be really
> appreciated.
> Thanks
>
> Dominique
>
> Dom_at_cheerful.com

Use 'DD-MM-RRRR'. You only had 3 R's rather than 4. I use this mask with 7.3.3 in several applications with no problem using century or not.

MR. Received on Tue Jul 07 1998 - 11:07:44 CDT