We had someone at our local user's group meeting ( Austin, TX ) that was
showing off Reporting Services. I asked him the same question you just asked
and he said it was not possible.
It seems with the scripting functionality, it should be possible to do some
form of server-side validation where at a minimum you can prevent the report
from running if an invalid parameter was entered. I've only just started
playing with RS today, so I cannot offer any other assistance.
-Robert
[quoted text, click to view] "BootieDay" wrote:
> Is there a method for doing simple validation of report parameters? I would
> like to limit numeric input, for example, to a min/max range. Also, I would
> like to apply an input mask. (what I'm actually trying to do is provide an
> input parameter for IP address, in the format xxx.xxx.xxx.xxx) so that the
> user can define a range. In this example, I would like to test each xxx
> octet for a valid value (0-255) and also to prevent the user from overwriting
This should theoretically be easy. Four paramaters - one for each octet - that
will accept a Min value of 0 and a Max value of 255. A variable that then
concatenates them with a period between each parameter.
GeoSynch
[quoted text, click to view] RobertP wrote:
> We had someone at our local user's group meeting ( Austin, TX ) that was
> showing off Reporting Services. I asked him the same question you just asked
> and he said it was not possible.
>
> It seems with the scripting functionality, it should be possible to do some
> form of server-side validation where at a minimum you can prevent the report
> from running if an invalid parameter was entered. I've only just started
> playing with RS today, so I cannot offer any other assistance.
>
> -Robert
>
> "BootieDay" wrote:
>
>> Is there a method for doing simple validation of report parameters? I would
>> like to limit numeric input, for example, to a min/max range. Also, I would
>> like to apply an input mask. (what I'm actually trying to do is provide an
>> input parameter for IP address, in the format xxx.xxx.xxx.xxx) so that the
>> user can define a range. In this example, I would like to test each xxx
>> octet for a valid value (0-255) and also to prevent the user from overwriting
>> the "." separators.
I thought of that and tried it, but am still not clear on how to limit the
range entered. Also, the size of the parameter fields is huge making this
type of entry look really clumsy. Is there a way to control the displayed
size of the input field?
[quoted text, click to view] "GeoSynch" wrote:
> This should theoretically be easy. Four paramaters - one for each octet - that
> will accept a Min value of 0 and a Max value of 255. A variable that then
> concatenates them with a period between each parameter.
>
>
> GeoSynch
>
>
> RobertP wrote:
>
> > We had someone at our local user's group meeting ( Austin, TX ) that was
> > showing off Reporting Services. I asked him the same question you just asked
> > and he said it was not possible.
> >
> > It seems with the scripting functionality, it should be possible to do some
> > form of server-side validation where at a minimum you can prevent the report
> > from running if an invalid parameter was entered. I've only just started
> > playing with RS today, so I cannot offer any other assistance.
> >
> > -Robert
> >
> > "BootieDay" wrote:
> >
> >> Is there a method for doing simple validation of report parameters? I would
> >> like to limit numeric input, for example, to a min/max range. Also, I would
> >> like to apply an input mask. (what I'm actually trying to do is provide an
> >> input parameter for IP address, in the format xxx.xxx.xxx.xxx) so that the
> >> user can define a range. In this example, I would like to test each xxx
> >> octet for a valid value (0-255) and also to prevent the user from overwriting
> >> the "." separators.
>
>
The parameter takes a query as a source. You could have a table with 0-255
in it that all 4 octets pull their possible values.
[quoted text, click to view] "BootieDay" wrote:
> I thought of that and tried it, but am still not clear on how to limit the
> range entered. Also, the size of the parameter fields is huge making this
> type of entry look really clumsy. Is there a way to control the displayed
> size of the input field?
>
> "GeoSynch" wrote:
>
> > This should theoretically be easy. Four paramaters - one for each octet - that
> > will accept a Min value of 0 and a Max value of 255. A variable that then
> > concatenates them with a period between each parameter.
> >
> >
> > GeoSynch
> >
> >
> > RobertP wrote:
> >
> > > We had someone at our local user's group meeting ( Austin, TX ) that was
> > > showing off Reporting Services. I asked him the same question you just asked
> > > and he said it was not possible.
> > >
> > > It seems with the scripting functionality, it should be possible to do some
> > > form of server-side validation where at a minimum you can prevent the report
> > > from running if an invalid parameter was entered. I've only just started
> > > playing with RS today, so I cannot offer any other assistance.
> > >
> > > -Robert
> > >
> > > "BootieDay" wrote:
> > >
> > >> Is there a method for doing simple validation of report parameters? I would
> > >> like to limit numeric input, for example, to a min/max range. Also, I would
> > >> like to apply an input mask. (what I'm actually trying to do is provide an
> > >> input parameter for IP address, in the format xxx.xxx.xxx.xxx) so that the
> > >> user can define a range. In this example, I would like to test each xxx
> > >> octet for a valid value (0-255) and also to prevent the user from overwriting
> > >> the "." separators.
> >
> >
Don't see what you're looking for? Try a search.
