Re: Forms 3.0, Rpt and Year 2000

From: Alexander Robert Graf <agraf_at_sfu.ca>
Date: 9 Jul 1998 21:52:38 GMT
Message-ID: <6o3e36$bnc$1_at_morgoth.sfu.ca>


For Forms 3.0. the solution Oracle gave in the White Paper doesn't work on Feb 29 2000.

a

Henk de Wilde (dewildeh.THOU_SHALT_NOT_SPAM_at_xs4all.nl) wrote:
: On Sat, 04 Jul 1998 13:14:37 GMT, ironmtn_at_my-dejanews.com wrote:

: The principle is to let all date conversions be done in the database
: with one of Oracle's new "RR" format string. As long as the original
: developers used the DATE column type for dates that should solve your
: problem.

: Of course, you will have to scan your applications to see what other
: techniques might have been used.

: For rpt it is probably sufficient to scan for "TO_DATE", change the
: format mask to the equivalent "RR" mask and then scan all uses of the
: involved variables. If you have less than say 50 rpt sources, or when
: there are many differences in coding style this is probably best done
: by hand.

: For Sql*Forms 3 you need two procedures, one to fix all dates without
: a time component, one to fix the ones with a time component. Oracle
: has a white paper somewhere that describes how to build these
: procedures using SELECT... FROM DUAL;. It is possible to work out
: something similar with the PL/SQL string functions that does not need
: to go to the database, and so performs a little better.

: One important bug :
: All DATE fields will have to be changed to DATETIME. Else the
: procedure will not help.

: Once these procedures have been created all dates will have to be
: subjected to them. Of course this leaves open all instances where a
: date has not been treated as such..

: I hope this helped.

: --
: Henk de Wilde
Received on Thu Jul 09 1998 - 23:52:38 CEST

Original text of this message