You cannot modify the UI. With RS 2005 there is a datepicker. I would
suggest that they change the UI to the user picking from the calendar. If
they insist they have to have it the old way then they are asking for it to
be more expensive. You would have to create your own front end instead of
using report manager.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
[quoted text, click to view] "Jason L Lind" <JasonLLind@discussions.microsoft.com> wrote in message
news:2F5B54AB-50EC-4837-A110-39214E38B744@microsoft.com...
> But what about the UI logic? What is to prevent my user from entering in a
> start date and a week, when they can only enter a (start date and an end
> date) or a week or a month. Also the month paremeter, which I developed as
> a
> list/value does not want to take null as an option.
>
> Thank you,
>
> Jason
>
> "Bruce L-C [MVP]" wrote:
>
>> You would need to have the parameters be text and then have code behind
>> report that translates them appropriately. For instance, when mapping the
>> query parameter to the report parameter instead of sending the parameter
>> directly you map it to an expression that calls your code
>>
>> = code.convertdate(Parameters!FromParameter.value)
>>
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Jason L Lind" <JasonLLind@discussions.microsoft.com> wrote in message
>> news:38C5028A-1AC6-4376-A84F-6C8172CBFCC4@microsoft.com...
>> > Hi, I am investigating moving one of my client's reports from ASP 3.0
>> > based
>> > to RS 2005. Many of their reports have Paremeter "Groups" such that a
>> > report
>> > can be displayed by entering a daterange, a week number or a month. The
>> > stored procs are designed to only take the daterange paremeters and the
>> > ASP
>> > generates that range if the user entered a week or a month.
>> >
>> > I am not seeing a clean way to implement this in RS2005, is there?
>> >
>> > Thank you,
>> >
>> > Jason Lind
>>
>>
>>
