We recently upgraded from 5.1.3 to 6.1b.
The issue is that when a condition is set on any numeric object (dimension, detail, measure), if the number contains a decimal point then it’s converted to a comma instead.
I checked my Regional settings and they’re OK.
This does not happen if I use the old version of BO.
ramirezr (BOB member since 2004-02-13)
There are some formating issues with 6.1b.
Are you using the report that was already built in older version or are you creating a new report from scracth. Make sure you have the hotfix 074 installed on the server as well as client machine.
BOB User 
(BOB member since 2003-06-03)
It happens on every document. Both, old and new.
ramirezr (BOB member since 2004-02-13)
I have exactly the same problem in 6.1.3. Still no solution in sight.
cashworth (BOB member since 2005-02-09)
Have you tried to change the regional settings of your “Windows”?
I had some problem of the same kind with BO 6.5, but I don’t know about BO 6.1
elallema 
(BOB member since 2004-12-23)
What is the Language version of your BO Installation ?
mada 
(BOB member since 2004-11-25)
did you check the parameter in your Universe? each universeconnection has it’s own parameter tab in Version 6 … and I had customers with settings that changed the decimals for their oracle universes there…
I bet that’s the issue here…
we changed designer universecon param: DECIMAL_COMMA to NO
wobi… i think I got the flu… brrh…
Wolfgang Bidner 
(BOB member since 2002-08-30)