Devart Forums

Please note the following code

var
fPrice:Currency;
begin
//UniDAC
fZJE:=0.185;
UniQuery1.Append;
UniQuery1.FieldByName('fPrice').AsCurrency:=fPrice;
ShowMessage(FloatToStr(UniQuery1.FieldByName('fPrice').AsCurrency));
//Result is 0.18

//ADO
ADOQuery1.Append;
ADOQuery1.FieldByName('fPrice').AsCurrency:=fPrice;
ShowMessage(FloatToStr(ADOQuery1.FieldByName('fPrice').AsCurrency));
//Result is 0.185

//BDE
Query1.Append;
Query1.FieldByName('fPrice').AsCurrency:=fPrice;
ShowMessage(FloatToStr(Query1.FieldByName('fPrice').AsCurrency));
//Result is 0.19

//fPrice FieldType is Numeric(12,2)
________
Apple games

The field scale is 2. So the value is rounded to 2 digits.

Plash wrote:The field scale is 2. So the value is rounded to 2 digits.

but Should be rounded (0.19)

Plash wrote:The field scale is 2. So the value is rounded to 2 digits.

but Should be rounded (0.19)

Computer rounding functions do not use this mathematical rule. See the description of the RoundTo function in the Delphi help.

Yes! Delphi sure there is such a treatment!

However, in general we all hoped that the outcome is equal to = 0.19.

I think that if we can add an attribute as an option is equal to 0.18 or 0.19 is not better?

For example: default is 0.19, you can also choose to use delphi algorithm 0.19

You should not rely on the ODAC behaviour because it is implementation dependent.

You should round values yourself if it is important for you.