Re: Y2K issues

[Darrin Saxton <dssaxton@MINDSPRING.COM>]

What format does Oracle return the date in if you do a straight SQL (NOT
SQR) select of a date with no formatting?
Does it have the century in it or not.  If not then talk to your DBA about
changing Oracle's native date format to include the century.

> Following is the details of our SQR version
> SQR/4.0.2/IBM RS6000/AIX 4.1/Oracle 7.2.3/May 02 1997
>
> When we tested for Y2K compliance of our SQRIBE version using function
>
> DATEADD(datenow(),'year',6)
>
> and then printing the new date with the edit mask 'DD/MM/YYYY' ,
> it was displaying the year as 1905 instead of 2005.
>
> We have checked up in the ORACLE by using to_char(dd-mon-yyyy) which
> returns 2005.
>
> When the edit mask of the new date was changed to 'DD/MM/RR' the output
for
>  year was 05
> and with the edit mask 'DD/MM/RRRR' it was displaying the year as 0505
>
> We tried to add the following default settings in the SQR.INI file but
> without any success.
>
> UseY2kCenturyAlgorithm  = TRUE
> OutputTwoDigitYearWarningMsg = FALSE
>
> This may be possibly because these settings are compatible only for SQR
> version 5.0.
>
> Please advice on what should be the procedure followed for being Y2K
> compliant for our
> SQRIBE with version 4.0.2
>
> Following were the codes written for checking Y2K compliance
> let $inp_date =  DATEADD(datenow(),'year',6)
> print $inp_date (2,1) edit 'DD/MM/YYYY'
>
> please help
>
***************************************************************************
> **********************************
>
>
> Hi Saurabh,
>         When you say that you did the Oracle 'RR' thing I assume that you
> mean you changed your Oracle NLS date format. This will take care of
> inserts
> into the data base and most other stuff where you are dealing directly
with
> Oracle functions that do not have SQR variables involved. Be careful when
> using the Oracle between function on dates that have been assigned to SQR
> variables. Make sure that you mask the variables using the to_date
function
> like to_date(&some_date,'dd-mon-rr') or what ever your default date mask
> is.
> You will also need to do this where any comparison operators are used in
> your SQL queries, such as >=, < etc. Hope this helps.
>
> Dan.
>
>         ******************************************
>         Hello Everybody.
>
>         I have recently been assigned a task where SQRIBE is used for the
> report
>         purposes. The project has not gone live as of now and so this area
> was a
>         little neglected. Thus this delay in the following action.
>
>         Being a naive user, I have tried to fine out the version of SQRIBE
> that I
>         am using and the resultant reply that I am getting is :
>         " SQR/4.0.2/IBM RS6000/AIX 4.1/Oracle 7.2.3/....."
>
>         Hope this clarifies the platform on which I am working.
>
>         What I would like to know is  -  what do I have to check/ensure to
> be sure
>         of SQRIBE working fine in Y2K. I have done the masking for ORACLE
> to
> 'RR'
>         and I want to know what else I have to do for SQRIBE.
>
>         Regards and wish you all a merry Xmas !!.
>
>         Saurabh.