March 11, 2015 at 8:15 am
In the SSRS reporting interface I just changed the user input fields ( 2 of them ) to be datetime so that user can use the calendar control. That is cool.
However when I run the report... No results.. Why ?
Earlier the user would have to type 20140101 and 20150330 as input and the report ran well.
/*
Alter PROCEDURE rpt_tee_info( @start_date varchar(10) , @end_date varchar(10) )
as
Begin....
*/
March 11, 2015 at 10:08 am
mw112009 (3/11/2015)
In the SSRS reporting interface I just changed the user input fields ( 2 of them ) to be datetime so that user can use the calendar control. That is cool.However when I run the report... No results.. Why ?
Earlier the user would have to type 20140101 and 20150330 as input and the report ran well.
/*
Alter PROCEDURE rpt_tee_info( @start_date varchar(10) , @end_date varchar(10) )
as
Begin....
*/
Pretty sparse on details here but I suspect it is because you didn't change your parameters in your procedure. You changed the report parameters to datetime but when you implicitly convert that to varchar(10) you are not going to get a valid datetime. Change your parameter datatypes and see if that is the problem.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply