Re: Y2K issues

[sgour <sgour@STOCKHOLDING.COM>]

Hi.

Thanks to all of you for your invaluable suggestions.
It is the time difference between our places that gives such a
long gap between our communication.

As suggested  by Benjamin, the code showed the correct date (30/12/2005 as
today) on our system. Thanks again.

Mark, the current date on our AIX box is
Thu Dec 30 12:07:04 CUT 1999

Reminding you again the details of our SQR version is
SQR/4.0.2/IBM RS6000/AIX 4.1/Oracle 7.2.3/May 02 1997

With this versions is it possible to add the following default settings in
the SQR.INI file

UseY2kCenturyAlgorithm  = TRUE
OutputTwoDigitYearWarningMsg = FALSE

I know that this being used for ver 5 of SQRIBE


Darrin, regarding the oracle date format, it is duly masked
and is taking care for the year. egs are given below:

select TO_CHAR(sysdate, 'DD-MON-YYYY') from dual ;
30-DEC-1999

select TO_CHAR(sysdate+5, 'DD-MON-YYYY') from dual ;
04-JAN-2000



Hi Saurabh

Try this to check Y2K and see how it comes up on your system. It shows the
correct date (29/12/2005 as today) on ours.

let $date=datetostr(dateadd(datenow(),'year',6),'DD/MM/YYYY')
show $date

At 08:37 PM 12/29/99 +0530, you wrote:
>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.


Ben Le
ITS - Sylvania CC-224
Voice:(503)-977-4970  Fax:(503)-977-4987
Mailto:ble@pcc.edu