Rounding Language dependend?

Kappe
Kappe Member Posts: 64
Hello

I have a problem with the rounding in a NAV 4 SP3 database.

In a General Journal I have an Amount of f.ex. 3,75.
When I want to post this I get an Error from CU12.
Amount (LCY) <> Round(Amount(LCY))
if 3,75 <> 4 then ... Error

This is when I select DAN or DEU language in the client.
When I switch the client to ENU, it works!
if 3,75 <> 3,75 then ... Error

:-k

Has anybody a clue how this can happen?

:bug: ?

CU1.ReadRounding returns allways the same value.

Regards
Kappe
___________________________________________

Kappe

Comments

  • Mbad
    Mbad Member Posts: 344
    Was there any modifications made to table 81 or cu 11, 12 and 13? Or maybe in currency? Cant see how changing language can affect this in standard.
  • andreof
    andreof Member Posts: 133
    Navision Documentation:

    "
    This optional parameter determines the precision used when rounding. The default value is 0.01 for the US version. In other countries, other default values may be used. Note that the default value is only used when you have not specified the rounding precision in the Amount Rounding Precision field in the General Ledger Setup table."
    Andre Fidalgo
    My world: Dynamics NAV,SQL and .NET

    CEO at Solving Dynamics
    http://www.solvingdynamics.com
  • Kappe
    Kappe Member Posts: 64
    Hello

    Thanks for the fast reply.

    @Mbad
    Yes. CU 12 & 13 contain Efaktura and PM Add-On from Celenia (Version List).
    CU 11 & 81 I must check
    T 4 Currency is not modified

    I have the same problem, that I can't see how the language could affect this. :wink:

    @ andreof
    Thanks, I did use the search at the board and I tested it with different values in General setup.
    So this is why I created a new forum entry.

    Regards
    Kappe
    ___________________________________________

    Kappe
  • Kappe
    Kappe Member Posts: 64
    Solved it! \:D/

    Changed the Value in General Setup within a report permanent.
    Changing it in the form behaved different....

    So andreof was on the right track :wink:

    This solved the problem - it seems to be an old upgrade issue. :-k

    Regards
    Kappe
    ___________________________________________

    Kappe