OWC11 - ChartSpace bug with formatted values ?

[Antoine Prevot]

Hi,

Here's my problem :

I have a PivotTable connected to an AS2005 cube.
I have a Chart linked to my PivotTable.

When i use simple values (decimals) everything works fine.
When i use a formatted measure, ie a currency (FormatString is #,#.00), i
can see the different values in the PivotTable, but they are zeroed in the
Chart !

Any tips about this ?

Thanks in advance,

 

[Antoine Prevot]

Here's some details :

The formatted measure isn't a currency but a simple amount, a decimal value
formatted to appear accordingly to the user language preferences, ie:

A value of 42000,5890 will be displayed as :
42,000.58 (US format)
42 000,58 (European format)

I tried to get this value in US format, but in a European windows profile
(french), the value displayed in the Chart is 42,00058 (not 42000,58 !). When
i get back in a US profile, the value is correct and appears in the Chart.

It's problematic because a customer can have his workstation configured in
his own location profile (spain, france, germany ...), and have his reporting
application configured to display US formatted informations (caused by a
group policy).

I tried to force a lang (lcid) directly in the MDX statements generated (ie
using LANGUAGE='1033'), unfortunately the OWCs 11 doesn't seem to understand
this syntax ... it's a shame, the SQL management studio does, i guess i'm
doomed

Any help would be appreciated !

 

[Alvin Bruney - ASP.NET MVP]

that's, as far as i know, an excel limitation. not really the fault of the
owc

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006

 

[Antoine Prevot]

Ok, thanks Alvin !

I'm now forcing numeric & date formats by using some registry tricks, so
that the application formatted values are consistent with the user profile. I
couldn't find any other way :-/

--
-= Tonio =-

that's, as far as i know, an excel limitation. not really the fault of the
owc

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006