Bug in version 3.0.13.2?

[Sam Spritzer <SSpritzer@GW.CTG.COM>]

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