SQL Server Performance

Currency Symbol Problem

Discussion in 'SQL Server 2005 Reporting Services' started by Toni, Apr 20, 2006.

  1. Toni New Member

    I am currently writing a report in SQL 2005 RS and have a problem with the format of a currency field. I am creating the report through the 'SQL Server Business Intelligence Development Studio'

    In the report preview (and live) it shows the prefix for the field to be $, and yet when I look at the custom format for the field it shows it as being Format Currency and the sample shows the output will be £1,234.00.

    If I change the format to percentage or whatever it does exactly what you would expect it to do.

    I have checked all the regional settings on my machine to UK in the various places you can and still it wants the result to be dollars. I have set the language options in Windows and SQL server to UK and 23 respectively.

    Anybody, help please!!!!

    Toni Chaffin
    aka Toni
  2. Toni New Member

    Problem Solved:- I noticed that in the properties for the textbox, under 'International' there was a setting for 'Language', so I selected all of the offending boxes and changed their International properties from Default (U.S. I guess) to English (United Kingdom), and bingo, problem solved.


    Toni Chaffin
    aka Toni
  3. Adriaan New Member

    Here's to hoping you don't have to support a multi-currency system.[<img src='/community/emoticons/emotion-1.gif' alt=':)' />]
  4. Toni New Member

    Yeah Ok, Thanks for that. Nightmare scenarios like that you can keep to yourself <img src='/community/emoticons/emotion-5.gif' alt=';)' /><br /><br />I see you point though. out of curiousity, what would have been the solution if that was the case?<br /><br />Regards<br /><br /><br /><br />Toni Chaffin<br />aka Toni
  5. Adriaan New Member

    You'd need separate columns in your data structure to store the currency for the amount. You could also use a purely numeric equivalent data type instead of currency, to avoid the currency symbol popping up everywhere.

    Not really a nightmare scenario, just sensible database design.
  6. Toni New Member

    Thanks for that. I am purely UK at the moment. Once I have this phase of the project out of the way I shall start to look at converting the DB to accomadate that just in case the scenario does rear its head again.

    Kindest Regards

    Toni Chaffin
    aka Toni

Share This Page