>>I just underline and make blue the text for the link.
>>However, the link is there for pdf, excel etc.
Exactly, and that is why I was hoping there was a simple way to prevent it.
right now... ;-)
"Bruce L-C [MVP]" wrote:
> I just underline and make blue the text for the link. However, the link is
> there for pdf, excel etc.
>
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Chris G." <ChrisG@nospam.nospam> wrote in message
> news:0E8BEBC8-8B84-4BAC-A0E5-851A3E449C75@microsoft.com...
> > Hi Wei,
> >
> > Thank you for all of the information.
> >
> >>>If you open a web site like
> >>>
http://www.microsoft.com/careers/default.aspx,
> >>>you could see all the links in the left panel have a underline. Then,
> >>>when
> >>>you try to print this page, you could also find the underline in the
> >>>print
> >>>view. That means the printer will print exactly all the content you see
> >>>in
> >>>the page.
> >
> > I understand what you are saying. What I was looking for was a feature
> > that
> > is like the one in the Actuate reporting tool. In the Actuate tool, when
> > you
> > define a link in a report, it is automatically rendered (visually
> > formatted)
> > as a hyperlink when output to DHTML format, but when rendered to printing
> > formats such as PDF, etc. appear as plain text.
> >
> > There are merits to both approaches, but I was trying to do with SSRS what
> > I
> > can do in the Actuate tool.
> >
> >>>In the report, if you use the jump to property, the user will get the
> >>>cursor changed to be a hand when move the cursor on to it.
> >>>I think this will notify them that the text could navigate to a url.
> >
> > The problem is there would be no immediate visual cue as to which fields
> > are
> > hyperlinks. The user would have to hover the mouse over each field which
> > is
> > not very user friendly.
> >
> >>>Also, the print is not a render extension in the reporting services. So
> >>>you
> >>>could not write code to control the print behavior in reporting services.
> >
> > Understood.
> >
> > QUESTION: But what about the PDF render extension? Could I eliminate the
> > hyperlink formatting when the report is rendered to PDF?
> >
> >>>Another choice is you could use the Report Web Services to export the
> >>>report to a HTML file and then, you could apply a CSS file on it. You
> >>>could
> >>>specify the <a> tag in the HTML to have a hover format which is underline
> >>>and the common format without underline.
> >
> > True, but lots of custom coding is beyond the scope of the project I am
> > working on.
> >
> > --
> > Chris, SSSI
> >
> >
> > "Wei Lu [MSFT]" wrote:
> >
> >> Hi Chris,
> >>
> >> If you open a web site like
> >>
http://www.microsoft.com/careers/default.aspx,
> >> you could see all the links in the left panel have a underline. Then,
> >> when
> >> you try to print this page, you could also find the underline in the
> >> print
> >> view. That means the printer will print exactly all the content you see
> >> in
> >> the page.
> >>
> >> In the report, if you use the jump to property, the user will get the
> >> cursor changed to be a hand when move the cursor on to it.
> >> I think this will notify them that the text could navigate to a url.
> >>
> >> Also, the print is not a render extension in the reporting services. So
> >> you
> >> could not write code to control the print behavior in reporting services.
> >>
> >> Another choice is you could use the Report Web Services to export the
> >> report to a HTML file and then, you could apply a CSS file on it. You
> >> could
> >> specify the <a> tag in the HTML to have a hover format which is underline
> >> and the common format without underline.
> >>
> >> Sincerely,
> >>
> >> Wei Lu
> >>
> >> Microsoft Online Community Support
> >>
> >> ==================================================
> >>
> >> Get notification to my posts through email? Please refer to
> >>
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > >> ications.
> >>
> >> Note: The MSDN Managed Newsgroup support offering is for non-urgent
> >> issues
> >> where an initial response from the community or a Microsoft Support
> >> Engineer within 1 business day is acceptable. Please note that each
> >> follow
> >> up response may take approximately 2 business days as the support
> >> professional working with you may need further investigation to reach the
> >> most efficient resolution. The offering is not appropriate for situations
> >> that require urgent, real-time or phone-based interactions or complex
> >> project analysis and dump analysis issues. Issues of this nature are best
> >> handled working with a dedicated Microsoft Support Engineer by contacting
> >> Microsoft Customer Support Services (CSS) at
> >>
http://msdn.microsoft.com/subscriptions/support/default.aspx. > >>
> >> ==================================================
> >> (This posting is provided "AS IS", with no warranties, and confers no
> >> rights.)
> >>
> >>
>
>