Post reply

Report displaying numbers with dot separators instead of commas?!

  • July 28, 2015 at 9:12 am

    #310245

    Hello!

    I have a numeric field which I have attempted to configure to use a comma separator, however it is showing a dot separator instead. The field in SQL is decimal(26,6). This returns for example 17606.000000.

    In my report, I have configured it via text box properties to show no decimal places and to use a thousand separator (,). I have also tried using format '##,##' and 'n0' as usual.

    In all other reports (on the same server) using the exact same field and exactly the same method of formatting, it is displayed correctly (17,606) however on this report it is different (17.606)

    I tried creating a new report to test this out, using exactly the same stored procedure, the same parameters and the same expression (which is just sum(field) ) and it shows correctly as 17,606. So it cannot be the server configuration.

    I assume I've changed a simple setting in the RDL on accident - but I can't think what. It is happening on every numeric field in the report, but only in this report!

    Does anyone have any ideas please?

    LinkedIn

  • July 28, 2015 at 9:25 am

    #1815458

    SSRS is using the regional settings by default

    You have to force the langage on the properties of the rdl

    see the language property at the body of the report

    :w00t: !!!GOOGLE IS YOUR BEST FRIEND!!! :w00t:

  • July 28, 2015 at 9:32 am

    #1815464

    Hi Mohamed,

    Thankyou for the quick response!

    Unfortunately this is not the case - the number appears the same whether 'Use regional formatting' is ticked or unticked. The regional setting is 'English (United Kingdom)'.

    LinkedIn

  • July 28, 2015 at 9:42 am

    #1815470

    Okay I just deleted the item and added it into the project again (after taking a copy) and the problem seems to have gone away! :s

    Would still be interested to hear if anyone's encountered this before, seems a bit random!

    LinkedIn

  • July 28, 2015 at 9:54 am

    #1815476

    Good you solve it

    I think it comes from the rdl property which have a default language set up

    See this for more information:

    https://msdn.microsoft.com/en-us/library/ms159642(v=sql.105).aspx

    :w00t: !!!GOOGLE IS YOUR BEST FRIEND!!! :w00t:

  • July 28, 2015 at 10:01 am

    #1815480

    It doesn't look like it, as all regional/language settings were identical to all other RDLs (the default!)

    LinkedIn

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply