Date Formats and local IE settings

We have reports available on the web that take begin and end dates in US
format (i.e. 08/02/2004 for August 2, 2004). When our international
customers try to render the report the dates get converted to the date
setting they have on their local IE, so the date then looks like 02/08/2004
for August 2, 2004. The report then pulls back data for February 8, 2004.
Does anyone know of a work around for this?SP1 solves this with rs:ParameterLanguage URL access parameter. See:
http://download.microsoft.com/download/7/f/b/7fb1a251-13ad-404c-a034-10d79ddaa510/SP1Readme_EN.htm#_new_url_access_parameters
Just install SP1 and it will work, you don't need to do any changes in the
reports.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jessica C" <jesscobbe@.hotmail.com> wrote in message
news:%23ORisPleEHA.592@.TK2MSFTNGP11.phx.gbl...
> We have reports available on the web that take begin and end dates in US
> format (i.e. 08/02/2004 for August 2, 2004). When our international
> customers try to render the report the dates get converted to the date
> setting they have on their local IE, so the date then looks like
02/08/2004
> for August 2, 2004. The report then pulls back data for February 8, 2004.
> Does anyone know of a work around for this?
>|||Thanks for the quick response... I didn't know about that....
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:OzE4e4leEHA.3928@.TK2MSFTNGP11.phx.gbl...
> SP1 solves this with rs:ParameterLanguage URL access parameter. See:
>
http://download.microsoft.com/download/7/f/b/7fb1a251-13ad-404c-a034-10d79ddaa510/SP1Readme_EN.htm#_new_url_access_parameters
> Just install SP1 and it will work, you don't need to do any changes in the
> reports.
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Jessica C" <jesscobbe@.hotmail.com> wrote in message
> news:%23ORisPleEHA.592@.TK2MSFTNGP11.phx.gbl...
> > We have reports available on the web that take begin and end dates in US
> > format (i.e. 08/02/2004 for August 2, 2004). When our international
> > customers try to render the report the dates get converted to the date
> > setting they have on their local IE, so the date then looks like
> 02/08/2004
> > for August 2, 2004. The report then pulls back data for February 8,
2004.
> > Does anyone know of a work around for this?
> >
> >
>|||We tried setting rs:ParameterLanguage=en-US in the URL so international
users dates would stay in the MM/DD/YYYY format but it isn't working. We
have SP1 installed. Do you have any suggestions? Please help, our
customers in the UK would like to be able to view their reports. Thanks!
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:OzE4e4leEHA.3928@.TK2MSFTNGP11.phx.gbl...
> SP1 solves this with rs:ParameterLanguage URL access parameter. See:
>
http://download.microsoft.com/download/7/f/b/7fb1a251-13ad-404c-a034-10d79ddaa510/SP1Readme_EN.htm#_new_url_access_parameters
> Just install SP1 and it will work, you don't need to do any changes in the
> reports.
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Jessica C" <jesscobbe@.hotmail.com> wrote in message
> news:%23ORisPleEHA.592@.TK2MSFTNGP11.phx.gbl...
> > We have reports available on the web that take begin and end dates in US
> > format (i.e. 08/02/2004 for August 2, 2004). When our international
> > customers try to render the report the dates get converted to the date
> > setting they have on their local IE, so the date then looks like
> 02/08/2004
> > for August 2, 2004. The report then pulls back data for February 8,
2004.
> > Does anyone know of a work around for this?
> >
> >
>|||I assume you are talking about the date format in the parameters area. You
need to make sure the report language (a report property) is set to english
as well. Otherwise, it will adapt to the user locale.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jessica C" <jesscobbe@.hotmail.com> wrote in message
news:eef80tneEHA.3028@.TK2MSFTNGP12.phx.gbl...
> We tried setting rs:ParameterLanguage=en-US in the URL so international
> users dates would stay in the MM/DD/YYYY format but it isn't working. We
> have SP1 installed. Do you have any suggestions? Please help, our
> customers in the UK would like to be able to view their reports. Thanks!
>
> "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> news:OzE4e4leEHA.3928@.TK2MSFTNGP11.phx.gbl...
>> SP1 solves this with rs:ParameterLanguage URL access parameter. See:
> http://download.microsoft.com/download/7/f/b/7fb1a251-13ad-404c-a034-10d79ddaa510/SP1Readme_EN.htm#_new_url_access_parameters
>> Just install SP1 and it will work, you don't need to do any changes in
>> the
>> reports.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>> "Jessica C" <jesscobbe@.hotmail.com> wrote in message
>> news:%23ORisPleEHA.592@.TK2MSFTNGP11.phx.gbl...
>> > We have reports available on the web that take begin and end dates in
>> > US
>> > format (i.e. 08/02/2004 for August 2, 2004). When our international
>> > customers try to render the report the dates get converted to the date
>> > setting they have on their local IE, so the date then looks like
>> 02/08/2004
>> > for August 2, 2004. The report then pulls back data for February 8,
> 2004.
>> > Does anyone know of a work around for this?
>> >
>> >
>>
>

Date Format settings problem

We have set of (200 over) reports with date-formats selected as default date-format as in windows format - dd/MM/yyyy.

Reports are viewed through the viewer (CR version 9) on IE.

We install CR on a different machine which had a date format of MM/dd/yyyy and then realised after looking into the application that the reports were displaying the formats as what is in the control panel settings.

Though we change the settings and the reports when viewed through the designor is correctly displaying the format as expected but that does not seem to be the case when viewed through the viewer on IE.

But once you open one of the reports force a change and save back the settings for each date-columns it shows correctly even in the viewer.

We uninstalled CR (deleted registry entries in hkey_local_machine\software\ and deleted relevant folders) and re-installed back CR only to see no change.

Any ideas what this would be causing this problem?
Any help appreciated !

Regards,
Kaushik.Here is the solution
Create one formula in each report as 'DateFormat'
Edit formula write there 1

Now

Steps
1) Select DateField in your report - > Right Click -> CustomeStyile -> Customise -> Goto Order Frame click formula there - > insert your 'DateFormat' formula there.

Save the report.
Now it will work

2) Through Program pass formula field values
for DateFormat as 1 or 2 or 3

You will get Date in respective format.
Still you have problem ask me.

Thanks
Vilas

Date format independant of local settings

Hello,
how can we make the Date format for SQLServer7.0 independant of locale settings. We have a Web Server and a database server running multiple projects having different requirement for date formats viz mm/dd/yyyy and dd/mm/yyyy.

I suppose SQLServer takes the database local date format as the current date format. The problem can be solved if i can indicate in my SQL queries the format being used in the query. This also eliminates any accidental change in database server format (from mm/dd/yyyy to dd/mm/yyyy), which would mean 1st Feb being inserted into the database as 2nd Jan.

Any Ideas !!!

Regards,

AshutoshHave you looked at SET DATEFORMAT

SET DATEFORMAT mdy
GO
DECLARE @.datevar datetime
SET @.datevar = '12/31/98'
SELECT @.datevar
GO

SET DATEFORMAT ydm
GO
DECLARE @.datevar datetime
SET @.datevar = '98/31/12'
SELECT @.datevar
GO

SET DATEFORMAT ymd
GO
DECLARE @.datevar datetime
SET @.datevar = '98/12/31'
SELECT @.datevar
GO|||Hello,
thanks the problem seems to be solved by using the SET DATEFORMAT command. While ADODB connection object we have to execute the above command as a action query -
Connection.Execute "SET DATEFORMAT dmy"

The connection thus follows this new date format.

Thanks Again :-)

Regards,

Ashutosh|||This is only a problem with character date formats.
If you always transfer dates with format yyyymmdd then you should never have a problem.

dd mmm yyyy also works as long as you don't use other languages.

Date format in ms sql

I have computer with Serbian standards and formats (Regional Settings).

I use datepicker control to select date, but when I try to insert it into database (DatePicker1.Value) it throws error.

What should I set up in order to be able to insert date into ms sql 2000 database, without having to change Regional settings?

This is last question for tonight

Thanks,
Milan

If you use parameters, rather than trying to build up the SQL INSERT into a string.

http://aspnet101.com/aspnet101/tutorials.aspx?id=1

|||Very simple. nice and clean solution.

You just make me close bunch of open browser tabs and windows with Google's results

Thanks a lot.

Date Diffrent between "reports" & "reportserver"

I have a problem with the dates and "datetime" picker in my report
(sqlserver 2005 sp2).
My reginal settings on the server are: "hebrew" - "Isreal".
I have a report with a datetime picker.
If I'm opening the report from: http://myserver/REPORTSERVER and I'm
writting in the datepicker textbox the value "01/04/2008", and then
click on the calander icon it opens on the on the 4th of january 2008.
If I'm opening the report from: http://myserver/REPORTS and I'm
writting in the datepicker textbox the value "01/04/2008", and then
click on the calander icon it opens on the on the 1th of april 2008.
Does anybody know this bug and how to wotk with it?
Thanks.I'm not sure which is getting what you want. Is Reports getting you want you
want?
When you say opening it from reportserver how are you doing this? Are you
using URL integration in your app? Jump to URL from another Report? Or some
other way?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"nicknack" <roezohar@.gmail.com> wrote in message
news:bad0a977-4b16-4561-a661-ac0b35437d4b@.s37g2000prg.googlegroups.com...
>I have a problem with the dates and "datetime" picker in my report
> (sqlserver 2005 sp2).
> My reginal settings on the server are: "hebrew" - "Isreal".
> I have a report with a datetime picker.
> If I'm opening the report from: http://myserver/REPORTSERVER and I'm
> writting in the datepicker textbox the value "01/04/2008", and then
> click on the calander icon it opens on the on the 4th of january 2008.
> If I'm opening the report from: http://myserver/REPORTS and I'm
> writting in the datepicker textbox the value "01/04/2008", and then
> click on the calander icon it opens on the on the 1th of april 2008.
>
> Does anybody know this bug and how to wotk with it?
> Thanks.

Date and Language settings - SQL Server 2005

Despite the documentatin stating that SQL Server will pick up and use the locale settings, why will the database only accept entry in american (mdy) format?

MDY is the default datetime format in SQL Server.

You can change the format using "SET DATEFORMAT",

see help here: http://msdn2.microsoft.com/en-us/library/ms189491.aspx

Xinwei

|||Thanks,
I tried that and it didn't appear to do anything. I've got the ldefault language settings as British and all the examples were coming out in dmy displayed format despite changing the format.
The documentation (SQL Books) states that it should use the server locale.
I solved the problem using code to transform the date from a 'DateTime picker' into an acceptable format.
It was just an expression of frustration about the silly bugs in Microsoft products, especially the 2005 range (how about taking a comment as part of an enumeration, - VB 2005; not letting you move directly to row 0 in a BindingSource.DataSource, you have to MoveLast then MoveFirst - C# 2005; the ComboBox control spewing garbage out until it settles down, thus messing up any text or value changes; the setting the sorted property on a bound combobox sets the value returned to the position in the combobox list instead of the bound data value; The weird error messages often having nothing to do with the type and position of the error..... These are some of the recent value added features.