very interesting quirk -period where a comma should be for thousands

[jmh944911]

I have a very interesting thing going on in one of my reports. I have the same number format defined for detail and summary records in a report(standard with 0 decimal places). The formats display differently in the detail section the thousands seperator is a period in the summary it is as expected a comma. I have checked for conditional formating and verified that my fields are defined properly. I have also tried the format painter from sum to detail.

Example:

a 1.000
b 2.901
c 3.400
--------
7,301

I am stumpped.
comma
number format
period
european number format

 

[RuralGuy]

Hmmm...
What do you have your Windows (?) Regional Settings for Number and Currency set to?

 

[jmh944911]

Hmmm...
What do you have your Windows (?) Regional Settings for Number and Currency set to?

Good thinking but I looked there already.
The comma is my thousands seperator and the period is my decimal indicator.
I appreciate the assistance.

 

[Banana]

Does the behavior reproduce if you:

Create a blank database
Re-create the report with problem fields (from scratch, no cut and pasting)
Run the report

?

 

[jmh944911]

Good idea. I do not get the same problem in the new wizard/manual modified report. The actual report is very complex so this proves that somewhere in my complexity is the issue. You know... I used to have a philosophy that all the work should be done in the tables. Then I converted to a report guy and did all the work in the reports. I am too close to the trees to see the forest on this one. I can't think of what else to look for. It hits me as something to do with conditional formatting. What is odd is that my client would never want this format as such I would not make that switch just for the h3ll of it.