After searching and searching through this forum I have seen several similar
questions but no answers for my question so here it goes.
We have added front end screens for all of our reports. We also allow our
users to create subsciptions using these screens. For dates, our users would
like to enter "First day of the Current Fiscal Month". To compute this, it
requires a data base lookup.
In a perfect world I would be able to manipulate the input field (a date
that is defined as a string) convert it to the proper date, pass that in to
the SP and I would have my problem solved. However, I see no way to
manipulate an input parm.
I could code my SPs in such a way to handle this but I am using SPs that
already exist and accept dates as input parms. ADITTIONALLY, this doesn't
work for filters.
Is there a way to manipulate an input parm before it is used in the SP call?Yes there is. You can set your dataset source to an expression and the
expression can do any massaging you need it to do prior to calling the SP.
The downside of doing this is the field list not being populated so first
get the field list populated and then change it to an expression. In the
generic query designer do this:
= "mystoredproc " & code.yourcustomcode(parameters!parametername.value) &
etc
When I create custom code what I do is have a vb project with a textbox
(which will act as input to the code) and I develop the code in their so I
get all the nice debugging and development tools. Then I copy and paste into
RS.
HTH,
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ron Knott" <RonKnott@.discussions.microsoft.com> wrote in message
news:06347FC4-3E78-4C5B-A74D-7C458902F34B@.microsoft.com...
> After searching and searching through this forum I have seen several
> similar
> questions but no answers for my question so here it goes.
> We have added front end screens for all of our reports. We also allow our
> users to create subsciptions using these screens. For dates, our users
> would
> like to enter "First day of the Current Fiscal Month". To compute this,
> it
> requires a data base lookup.
> In a perfect world I would be able to manipulate the input field (a date
> that is defined as a string) convert it to the proper date, pass that in
> to
> the SP and I would have my problem solved. However, I see no way to
> manipulate an input parm.
> I could code my SPs in such a way to handle this but I am using SPs that
> already exist and accept dates as input parms. ADITTIONALLY, this doesn't
> work for filters.
> Is there a way to manipulate an input parm before it is used in the SP
> call?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment