Culture Settings Problem

Hi everyone,
My name is Ed Allison. I am very new to reporting services (about 2 weeks,
in between working on a lot of other stuff), and have had no luck attempting
to track down a particular problem.
I am running Visual Studio 2005 and Reporting Services 2005 on Windows XP
(fully service packed etc.), but the data source for my reports is SQL
Server 2000. I only use VS2005 for reports, as we are still on vs2003 for
the rest of our products. It looks as if, somewhere along the line, a
culture setting has been set wrong. This problem is occurring at the design
stage, i.e. I have not loaded the reports onto the report server.
I am working in the UK. I have double checked that my regional and language
settings under Control Panel and they are set to English(UK).
Under Tools>Options>Environment>International Settings, Language is set to
'Same as Microsoft Windows'.
Whenever I format to currency (using "C" as the formatstring, generally),
the amount is returned in $, not £. Whenever I have date parameters on a
stored procedure for a report dataset, the dates are initially registered in
UK format (dd/mm/yyyy), but as soon as I click the 'view report button', the
dates are set in the parameter windows to mm/dd/yyyy format. This causes an
error when such a conversion yields an invalid date, e.g. '30/01/2006' to
'01/30/2006'.
I have searched in vain around visual studio 2005 for anything relating to a
culture setting specific to it without success. I have also tried MSDN and
Books Online, but no luck. I have checked every user account on my local
machine to see if one was entered with US culture settings, but no luck.
Report Services Configuration also does not appear to mention culture.
If anyone could help, I would be most grateful.
Ed AllisonI have found the solution to this, and am thoroughly embarrassed to have
missed it.
For the sake of anyone new like me who has a similar problem with their
culture settings apparently being ignored - there is a Language property on
the Report that defaults to English(United States). If this is set to the
global User.Language, formatting will correspond to culture settings on the
report client. This property is also present in individual textboxes.
"Ed Allison" <ed@.optix.co.uk> wrote in message
news:ODg7mZbJGHA.2628@.TK2MSFTNGP15.phx.gbl...
> Hi everyone,
> My name is Ed Allison. I am very new to reporting services (about 2
> weeks, in between working on a lot of other stuff), and have had no luck
> attempting to track down a particular problem.
> I am running Visual Studio 2005 and Reporting Services 2005 on Windows XP
> (fully service packed etc.), but the data source for my reports is SQL
> Server 2000. I only use VS2005 for reports, as we are still on vs2003 for
> the rest of our products. It looks as if, somewhere along the line, a
> culture setting has been set wrong. This problem is occurring at the
> design stage, i.e. I have not loaded the reports onto the report server.
> I am working in the UK. I have double checked that my regional and
> language settings under Control Panel and they are set to English(UK).
> Under Tools>Options>Environment>International Settings, Language is set to
> 'Same as Microsoft Windows'.
> Whenever I format to currency (using "C" as the formatstring, generally),
> the amount is returned in $, not £. Whenever I have date parameters on a
> stored procedure for a report dataset, the dates are initially registered
> in UK format (dd/mm/yyyy), but as soon as I click the 'view report
> button', the dates are set in the parameter windows to mm/dd/yyyy format.
> This causes an error when such a conversion yields an invalid date, e.g.
> '30/01/2006' to '01/30/2006'.
> I have searched in vain around visual studio 2005 for anything relating to
> a culture setting specific to it without success. I have also tried MSDN
> and Books Online, but no luck. I have checked every user account on my
> local machine to see if one was entered with US culture settings, but no
> luck. Report Services Configuration also does not appear to mention
> culture.
> If anyone could help, I would be most grateful.
> Ed Allison
>