[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index]
[Date Index]
[Thread Index]
[SQR-USERS Info]
[SQRUG Home Page]
Re: Strange Behaviour
Hello,
Thanks for the info. Got some questions . U had mentioned that this is a
Y2k message. And had mentioned that I may have to alter the date masks in
SQR.INI. (Presuming that SQR.INI contains date in YY instead of YYYY format
right ?). But that's not the case. variable SQR_DB_DATE_FORMAT contains the
value 'DD-MON-YYYY'.
Could you let me know why I get the problem. My SQR.ini for SQR Ver. 4.x
is attached.
(See attached file: sqr.ini)
Thanks in Advance.
Regards,
S.Srinivasan.
______________________________________
E-Mail : Srinivasan.Seetharaman@db.com
______________________________________
---------------------------------------- Message History
----------------------------------------
From: pobox@congruent.com.sg on 02/21/2001 02:25 PM GMT
Please respond to sqr-users@list.iex.net
To: SQR-USERS@list.iex.net
cc:
Subject: Re: Strange Behaviour
This message is a Y2K warning message generated by SQR when two-digit year
date masks are used. (The setting for this option affects the current report
and any new reports you create.)
You can alter the date masks by editing your SQR.INI file (or PSSQR.INI, if
you are using PeopleSoft). The database date mask should be the same as the
SQR date mask. Ideally, both of them should have 4 digit years, to prevent
any future Y2K warning messages.
Incidentally, in Brio Report Builder v6, you can turn off these warnings as
one of the options in the Brio Report Builder preferences. (In version 4.x,
your best bet is probably to use -XMB command line parameter - but this will
disable ALL error messages).
I can only gather that your company is a PeopleSoft customer, since you are
using SQR 4.x, which is quite an old version of SQR, but it is the version
that is bundled with PeopleSoft V7.x. Fortunately, in PeopleSoft 8, SQR V6
is bundled.
Regards,
Paul Hutton
Congruent Asia Pte Ltd
371 Beach Rd #13-06 Keypoint
Singapore 199597
Ph: +65 292 7412 Fax: +65 293 3018
http://www.congruentglobal.com
----- Original Message -----
From: <srinivasan.seetharaman@DB.COM>
To: <SQR-USERS@list.iex.net>
Sent: Wednesday, February 21, 2001 9:50 PM
Subject: Strange Behaviour
> Hello All,
> We had developed a SQR program . It was running well in Ver 3.x .
When running the same in Ver 4.x we got the following error message.
>
> *************************************************************************
> Warning on line 51:
> (SQR 7501) Using YY edit mask from (DD-MON-YY) against (2000)
>
> Warning on line 52:
> (SQR 7501) Using YY edit mask from (DD-MON-YY) against (2001)
> (SQR 5528) ORACLE OFEN error 1841 in cursor 5:
> ORA-01841: (full) year must be between -4713 and +9999, and not be 0
>
> Error on line 142:
> (SQR 3725) Bad return fetching row from database.
>
> SQR: Program Aborting.
> *************************************************************************
>
> On noting , we found that there are couple of input parameters(date
fields). From & Thru date(s). We also found that the field
"native-date-format" in
> setenv.sqc has different values in 3.x & 4.x. In 3.x it contains
YYYY-MM-DD HH:MI:SS while in 4.x it contains DD-MON-YYYY HH:MI:SS.
>
> Anyone knows why such a strange behaviour ?.
>
>
> Regards,
>
> S.Srinivasan.
> ______________________________________
> E-Mail : Srinivasan.Seetharaman@db.com
> ______________________________________
>
sqr.ini