parameter passing with blanks - help required

Hi,

I am having a curious problem with parameter passing between

reports. I have 2 reports the first report gives employee name, Department and

in the second report I have employee details. If the user clicks on the

Employee name in the First report it should go to the second report and display

the details. My problem comes if suppose the employee name is “Don King”when the parameter gets passed it does not recognize

the space between thename and throws

an error saying King not recognized.

Would appreciate if anybody could suggest as to how I can

pass the name with spaces in the report parameters.

Thanks and regards

PMNJPassing parameter with space to Jump to report and a subreport work fine. How are you passing this parameter around?|||am passing the parameter thru the report parameter

regards
PMNJ|||I'm having the same problem. I've also got a parameter which can be one word, of more than one word, sometimes with a comma in it. I'm passing the parameter, like PMNJ, thru the report parameter.

Has someone solved this problem?|||I reiterate Brad's question. How are you passing the parameter? Are you using Jump to Report? Are you parsing together a URL link? More details.|||Sorry, here is the info you requested.

I'm passing the parameter (along with another one) with the report parameter, orinating from a jump to report link.
The parameter is correctly displayed when using a textbox and a expression with the parameter in it.
But, when using this parameter in the MDX query for the dataset it doesn't work when the parameter consists of more than one word, i.e. there are spaces (blanks) in it.

If you need more details, please say so, I'll be happy to supply them.

parameter passing with blanks - help required

Hi,

I am having a curious problem with parameter passing between

reports. I have 2 reports the first report gives employee name, Department and

in the second report I have employee details. If the user clicks on the

Employee name in the First report it should go to the second report and display

the details. My problem comes if suppose the employee name is “Don King”when the parameter gets passed it does not recognize

the space between thename and throws

an error saying King not recognized.

Would appreciate if anybody could suggest as to how I can

pass the name with spaces in the report parameters.

Thanks and regards

PMNJPassing parameter with space to Jump to report and a subreport work fine. How are you passing this parameter around?|||am passing the parameter thru the report parameter

regards
PMNJ|||I'm having the same problem. I've also got a parameter which can be one word, of more than one word, sometimes with a comma in it. I'm passing the parameter, like PMNJ, thru the report parameter.

Has someone solved this problem?|||I reiterate Brad's question. How are you passing the parameter? Are you using Jump to Report? Are you parsing together a URL link? More details.|||Sorry, here is the info you requested.

I'm passing the parameter (along with another one) with the report parameter, orinating from a jump to report link.
The parameter is correctly displayed when using a textbox and a expression with the parameter in it.
But, when using this parameter in the MDX query for the dataset it doesn't work when the parameter consists of more than one word, i.e. there are spaces (blanks) in it.

If you need more details, please say so, I'll be happy to supply them.

Parameter bug in Service Pack 1

I'm just curious if Microsoft has officially recognized the bug in Service
Pack 1, where attempting to pass a hidden and a prompted variable to a
report generates a Javascript "Object expected" error.
Or is this still being researched? Anyone?
BrianWe are aware of this. It is a bug. It happens when a parameter that you
hide would normally have a null check box. If you can set the parameter to
non-nullable, that will fix the problem. Otherwise, there is no workaround.
--
This posting is provided "AS IS" with no warranties, and confers no rights
"G" <brian.grant@.si-intl-kc.com> wrote in message
news:eJaxcCMdEHA.2752@.TK2MSFTNGP12.phx.gbl...
> I'm just curious if Microsoft has officially recognized the bug in Service
> Pack 1, where attempting to pass a hidden and a prompted variable to a
> report generates a Javascript "Object expected" error.
> Or is this still being researched? Anyone?
> Brian
>|||Finally, confirmation.
Thank you Brian.
"Brian Hartman [MSFT]" <brianhartman@.hotmail.com> wrote in message
news:ub8NqxMdEHA.3988@.tk2msftngp13.phx.gbl...
> We are aware of this. It is a bug. It happens when a parameter that you
> hide would normally have a null check box. If you can set the parameter
to
> non-nullable, that will fix the problem. Otherwise, there is no
workaround.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
> "G" <brian.grant@.si-intl-kc.com> wrote in message
> news:eJaxcCMdEHA.2752@.TK2MSFTNGP12.phx.gbl...
> > I'm just curious if Microsoft has officially recognized the bug in
Service
> > Pack 1, where attempting to pass a hidden and a prompted variable to a
> > report generates a Javascript "Object expected" error.
> >
> > Or is this still being researched? Anyone?
> >
> > Brian
> >
> >
>|||I have another symptom associated with hidden parameters to report:
Reporting Services does not respond when attempting to view a report that
has both "Prompted Credentials" AND hidden parameters. The only work-around
that I have found is to make all parameters visible (i.e. prompted) when
selecting prompted credentials for the data source.
M
"G" wrote:
> Finally, confirmation.
> Thank you Brian.
> "Brian Hartman [MSFT]" <brianhartman@.hotmail.com> wrote in message
> news:ub8NqxMdEHA.3988@.tk2msftngp13.phx.gbl...
> > We are aware of this. It is a bug. It happens when a parameter that you
> > hide would normally have a null check box. If you can set the parameter
> to
> > non-nullable, that will fix the problem. Otherwise, there is no
> workaround.
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights
> >
> > "G" <brian.grant@.si-intl-kc.com> wrote in message
> > news:eJaxcCMdEHA.2752@.TK2MSFTNGP12.phx.gbl...
> > > I'm just curious if Microsoft has officially recognized the bug in
> Service
> > > Pack 1, where attempting to pass a hidden and a prompted variable to a
> > > report generates a Javascript "Object expected" error.
> > >
> > > Or is this still being researched? Anyone?
> > >
> > > Brian
> > >
> > >
> >
> >
>
>