Place one Chart on top of another one

I am trying to place one chart on top of another chart in report designer.
Everything looks go. So, I publish the report to Reporting Servers and for
some reason the graphs are placed next to one another instead of being on top
of each other. How can I fix this problem?
The reason why I am placing one chart on top of another chart is because I
can not figure out how to pass a value to CROSS AT property in a Bubble
chart. Does anyone know how to do this as well?
Thanks,
PeterHTML renderer does not support overlapping objects. You can try and render
it PDF or Jpeg and it will be overlapped, but not in HTML.
"Peter Revere" <PeterRevere@.discussions.microsoft.com> wrote in message
news:B9CBFE61-900D-4CD5-8712-CF3A8A72F6CA@.microsoft.com...
> I am trying to place one chart on top of another chart in report designer.
> Everything looks go. So, I publish the report to Reporting Servers and
for
> some reason the graphs are placed next to one another instead of being on
top
> of each other. How can I fix this problem?
> The reason why I am placing one chart on top of another chart is because I
> can not figure out how to pass a value to CROSS AT property in a Bubble
> chart. Does anyone know how to do this as well?
> Thanks,
> Peter|||Alexandre,
Thanks for the response. When I export the report to pdf is does work.
However, when I publish the report to Reporting Services the default viewer
is HTML. Is there away to set the default view in Reporting Services to PDF?
Peter
"Alexandre Mineev" wrote:
> HTML renderer does not support overlapping objects. You can try and render
> it PDF or Jpeg and it will be overlapped, but not in HTML.
> "Peter Revere" <PeterRevere@.discussions.microsoft.com> wrote in message
> news:B9CBFE61-900D-4CD5-8712-CF3A8A72F6CA@.microsoft.com...
> > I am trying to place one chart on top of another chart in report designer.
> > Everything looks go. So, I publish the report to Reporting Servers and
> for
> > some reason the graphs are placed next to one another instead of being on
> top
> > of each other. How can I fix this problem?
> >
> > The reason why I am placing one chart on top of another chart is because I
> > can not figure out how to pass a value to CROSS AT property in a Bubble
> > chart. Does anyone know how to do this as well?
> >
> > Thanks,
> > Peter
>
>|||If you are using URL access, add "&rs:Format=PDF" to the URL. You can read
about this in BOL in "Specifying a Rendering Format on a URL" underneath "URL
Access."
Ted
"Peter" wrote:
> Alexandre,
> Thanks for the response. When I export the report to pdf is does work.
> However, when I publish the report to Reporting Services the default viewer
> is HTML. Is there away to set the default view in Reporting Services to PDF?
>
> Peter|||Ted,
That worked thanks. I almost have it. This particular report has parameter
prompts. Is there away for the user to have the ability to pick there own
parameter values from the prompts or am I stuck hard coding in the values for
them?
"Ted K" wrote:
> If you are using URL access, add "&rs:Format=PDF" to the URL. You can read
> about this in BOL in "Specifying a Rendering Format on a URL" underneath "URL
> Access."
> Ted
> "Peter" wrote:
> > Alexandre,
> >
> > Thanks for the response. When I export the report to pdf is does work.
> > However, when I publish the report to Reporting Services the default viewer
> > is HTML. Is there away to set the default view in Reporting Services to PDF?
> >
> >
> > Peter
>|||Peter,
If you create a report parameter and don't specify any values, then the user
will get a text box where they can type anything. I think that's what you're
asking about -- usually people ask the opposite, how to create drop down
lists or how to fill those lists from a query. This is all well documented
in BOL, see the article "Using Parameters in a Report."
Ted
"Peter" wrote:
> Ted,
> That worked thanks. I almost have it. This particular report has parameter
> prompts. Is there away for the user to have the ability to pick there own
> parameter values from the prompts or am I stuck hard coding in the values for
> them?
> "Ted K" wrote:
> > If you are using URL access, add "&rs:Format=PDF" to the URL. You can read
> > about this in BOL in "Specifying a Rendering Format on a URL" underneath "URL
> > Access."
> >
> > Ted
> >
> > "Peter" wrote:
> >
> > > Alexandre,
> > >
> > > Thanks for the response. When I export the report to pdf is does work.
> > > However, when I publish the report to Reporting Services the default viewer
> > > is HTML. Is there away to set the default view in Reporting Services to PDF?
> > >
> > >
> > > Peter
> >