[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index]
[Date Index]
[Thread Index]
[SQR-USERS Info]
[SQRUG Home Page]
Re: Bug in version 3.0.13.2?
- Subject: Re: Bug in version 3.0.13.2?
- From: Victor Loghin <vgl_ca@HOTMAIL.COM>
- Date: Thu, 9 Dec 1999 11:57:52 EST
Sam,
Are you using PeopleSoft? If so, there is a procedure called PS_SQR_Round
(#in_decimal, #precision, :#out_decimal) in the number sqc.
The comment in the code is:
PS_SQR_Round
Rounds the input numeric value to the number of places specified
to the right of the decimal point. This routine is needed because
the SQR-provided round function is not totally reliable because it
does floating point to decimal conversion, which is inexact. This
routine implements MITI's suggested workaround to that problem.
HTH,
Victor Loghin
VGL Consulting Inc.
vgl_ca@hotmail.com
----Original Message Follows----
From: Sam Spritzer <SSpritzer@GW.CTG.COM>
Subject: Bug in version 3.0.13.2?
Date: Thu, 9 Dec 1999 08:07:57 -0500
Consider the scenario below...
BEGIN-PROCEDURE Process-No-Change
IF $Genl_Found = 'N'
LET $Error_Message = 'General deduction Not found'
DO Write-Error-Report
ELSE
IF &g.ded_addl_amt <> #Addl_Amt
LET $Error_Message = 'No change amount does not match current'
DO Write-Error-Report
END-IF
END-IF
END-PROCEDURE !Process-No-Change
**************************************************
Process-Change-Deduction
EMPLID xxxxx
Last Name xxxxx
$Genl_Found Y
&g.ded_addl_amt 45.1600000000000000000000
#Addl_Amt 45.1600000000000000000000000000000000
#Test -0.000000000000007000000000000000000
$Test -0.000000000000007
$Test2 45.16
Process-Change-Deduction is calling Terminate_Prior-Deduction
Terminate-Prior-Deduction
EMPLID xxxxx
Process-Change-Deduction is calling Case-New-Deduction
The value in #Addl_Amt is the result of the mainframe value 451F which was
converted using TRANSLATE and ROUND. I used an EDIT mask to string out the
decimals and as you can see, the 15th decimal position in #Addl_Amt is 0.
#Addl_Amt is then subtracted from &g.ded_addl_amt (read directly from the
database). And as #Test shows, there is a 7 in the 15th position.
The Brio website does not appear to have a list of known bugs. Has anyone
encountered such a situation?
SQRly yours,
Sam
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com