Drill Through Report -- Passing Date Parameters -- resulting in rsReportParameterTypeMismatch

All,

I have two reports. One is the main/summary report and other one is drill through. When I pass the Start and End Date parameters from main to the drill, the original format of DateTime changes. For example, in main report the data is displayed for following date range:

4/7/2007 - 5/9/2007 (i.e 4 July 2007 to 5 Sept 2007)

which displays correct data.

However, when I click on the drill through link, it jumps to the drill through report but displays data for the following period:

7/4/2007 - 9/5/2007 (i.e. 7 Apr 2007 to 9 May 2007)

The reporting services is converting the value from one format to another of the report parameters when passing them from parent report to the drill through. When run individually, these two reports display data for correct date range. And you can imagine, the child report crashes with rsReportParameterTypeMismatch error if the start or end date had a day part greater than 12 (e.g 25/4/2007).

I can't understand what could be going wrong. All the parameters in both reports are datetime, so intrisically, it shouldn't matter even if the reporting services is converting or using different date formats as long as the data type remains the same. Is there a way to fix this and force the parameters to stay in the format they are provided in the main report?

Your help is much appreciated.

Thanks.

Moved to Reporting Services forum.|||I thought I had posted it in SSRS forum? Anyways thanks.|||

People from Microsoft...Would you mind explaining this so very prevalent and confusing issue of Date time formatting? How to get around this issue of reporting services converting the date time to US format?

Just like the below post, I am using Canadian english as the regional settings. In the following post, someone says similar to what I am suggesting, Why does it matter when the datatype being used is DateTime all along and not string, then there shouldn't be any formatting issues? But the SSRS throws an error anyway.

http://www.eggheadcafe.com/forumarchives/SQLServerreportingsvcs/Jan2006/post25361489.asp

If someone has a solution to this, please advise.

|||

I found a related post discussing a similar issue:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=255248&SiteID=1

I think the reply by Lukasz P. in that thread may be the solution. Has any one tried it?