"Paul D. Johnson" <vpdj@yahoo.com> wrote in message
news:uFNkt1tXEHA.3156@TK2MSFTNGP12.phx.gbl...
>
>
> I have many reports which are currently run from stored procedures which
> take multiple parameters, but all reports include Client and User
parameters
> to limit the data returned to only that viewable by the User and only data
> the for those Clients (string list of integers (i.e., '1,2,5,7')).
>
>
>
> My question is whether there is any way to pass those parameters "behind
the
> scenes" so that the user does not see them on the ASP page in the report
> header.
>
>
>
>
> Any input would be appreciated.
>
>
>
> Thanks,
>
>
>
> n Paul D. Johnson
>
> n vpdj@NO_SP_AM_yahoo.com
>
>

"Bruce Loehle-Conger" <bruce_lcNOSPAM@hotmail.com> wrote in message
news:%23jN9xOuXEHA.3972@TK2MSFTNGP12.phx.gbl...
> There is a global variable that has the current user and that can be
access
> in your reports. I don't understand what you mean by client but you can
have
> parameters based on a query (for instance it could be based on the user)
and
> you can also hide those parameters from the user.
>
> Bruce L-C
>
> "Paul D. Johnson" <vpdj@yahoo.com> wrote in message
> news:uFNkt1tXEHA.3156@TK2MSFTNGP12.phx.gbl...
> >
> >
> > I have many reports which are currently run from stored procedures which
> > take multiple parameters, but all reports include Client and User
> parameters
> > to limit the data returned to only that viewable by the User and only
data
> > the for those Clients (string list of integers (i.e., '1,2,5,7')).
> >
> >
> >
> > My question is whether there is any way to pass those parameters "behind
> the
> > scenes" so that the user does not see them on the ASP page in the report
> > header.
> >
> >
> >
> >
> > Any input would be appreciated.
> >
> >
> >
> > Thanks,
> >
> >
> >
> > n Paul D. Johnson
> >
> > n vpdj@NO_SP_AM_yahoo.com
> >
> >
>
>

"Wolverine" <aking_sulat@yahoo.ca> wrote in message
news:uj8HPavXEHA.2664@TK2MSFTNGP09.phx.gbl...
> Maybe it is an on-demand report and the asp calls the report via URL. If
you
> do it this way, the param values are shown in the browser's title bar,
which
> users can see and experiment on pulling other "client's" reports. Behind
the
> scenes solution might be filtering the data by programmatically
> (ASP/ASP.NET) changing the default value of the "Client" and "Users".
>
> Any straightforward how-to for this?
>
> "Bruce Loehle-Conger" <bruce_lcNOSPAM@hotmail.com> wrote in message
> news:%23jN9xOuXEHA.3972@TK2MSFTNGP12.phx.gbl...
> > There is a global variable that has the current user and that can be
> access
> > in your reports. I don't understand what you mean by client but you can
> have
> > parameters based on a query (for instance it could be based on the user)
> and
> > you can also hide those parameters from the user.
> >
> > Bruce L-C
> >
> > "Paul D. Johnson" <vpdj@yahoo.com> wrote in message
> > news:uFNkt1tXEHA.3156@TK2MSFTNGP12.phx.gbl...
> > >
> > >
> > > I have many reports which are currently run from stored procedures
which
> > > take multiple parameters, but all reports include Client and User
> > parameters
> > > to limit the data returned to only that viewable by the User and only
> data
> > > the for those Clients (string list of integers (i.e., '1,2,5,7')).
> > >
> > >
> > >
> > > My question is whether there is any way to pass those parameters
"behind
> > the
> > > scenes" so that the user does not see them on the ASP page in the
report
> > > header.
> > >
> > >
> > >
> > >
> > > Any input would be appreciated.
> > >
> > >
> > >
> > > Thanks,
> > >
> > >
> > >
> > > n Paul D. Johnson
> > >
> > > n vpdj@NO_SP_AM_yahoo.com
> > >
> > >
> >
> >
>
>