THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Greg Low (The Bit Bucket: IDisposable)

Ramblings of Greg Low (SQL Server MVP, MCM and Microsoft RD) - SQL Down Under

SQL Reporting Services: be very careful with using "c" formatting for currency

While on site this week, another common problem that I see everywhere arose again.

When you need to format currency, you use the "c" format right? It's in nearly every set of course materials I've ever seen.

In many cases, that's wrong!

Take a long hard think about whether you really want the monetary values that you display automatically converting to the client system's currency. If you are reporting financial figures, for example, is it really appropriate that they should mysteriously suddenly change from dollars to yen because the client is based in Zama City rather than in New York City? Not likely. A million dollars in sales might be good but a million yen in sales not quite so good :-)

Published Friday, March 14, 2008 11:12 AM by Greg Low

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS



Rod Colledge said:

Nice tip Greg

March 14, 2008 5:52 AM

jerryhung said:

Good point, but only if the reports will be used "internationally" IMO

some reports may never leave a small town

March 14, 2008 9:28 AM

Greg Low said:

Hi Jerry,

Perhaps. I also see the same issue with ASP.NET web apps. I don't know what your equivalent of our trade practices department is like or your credit card agencies but I'll bet if I browsed a web site in the small town and it offered to sell me something for 1000 yen, I might have a hard time explaining why I charged your credit card for $1000.

I really struggle to see many times at all that "c" makes sense.



March 14, 2008 9:40 AM

Mike said:

So what is best practice?  

March 14, 2008 10:04 PM

Leave a Comment


This Blog



No tags have been created or used yet.


Privacy Statement