Re: Y2K and Forms 4.5

We are open bug because now Oracle don't support year more than 2137 on MS-Windows platforms.

Vladimir

In article <01be4fb6$39928b60$245f95c1_at_default>,   "Glenn Baron" <gbaron_at_dial.pipex.com> wrote:
> Hi all,
>
> According to reliable sources, Forms 4.5 is "Y2K compliant" . However, I
> have noticed some quirky behaviour when ASSIGNING date values in triggers.
>
> Perhaps someone could shed some light ?
>
> The basic situation is, in a d/b using "dd-mon-rr" default date format :
>
> I want to assign a (*very*) 'high' value to a forms date field, using the
> following syntax -
>
> :date_thing := '31-Dec-49 ;
>
> or
>
> :date_thing := to_date('31-Dec-2199','dd-mon-yyyy') ;
>
> where date_thing is an 11-character non-database date field in the form.
>
> I get some strange results, which I won't disclose here for fear of
> prejudicing your responses. I appreciate that some of the above could be
> considered "Son of Y2K", but we're desperate :)
>
> Cheers,
>
> Glenn Baron
>
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Thu Feb 04 1999 - 08:49:48 CET