I used to encounter this all the time with RoboHelp X5. And it coaxed me into developing what I feel is an interesting and more reliable approach.
Have you noticed that even on a fast intranet it seems to take an inordinate amount of time to open a PDF? I mean, with most of your topics, the user clicks and nearly instantly something happens. The topic generally loads right up in the topic pane. But a PDF, Word document or other file seems to take eons to load. Well, comparatively.
So I developed this thing I referred to as a "docfetch". Basically, I created regular RoboHelp topics. Linked those topics to the books pages or whatever. Then configured those topics to redirect to the PDF, Word document or other.
The expected benefit was that because I was now actually linking to topics in the project, those funky mysteriously broken links in the TOC disappeared. The unexpected side benefit was that users then saw an immediate response to clicking the link. I configured each of these topics to present some verbiage to the effect that they should please wait as the document was being opened. This put a stop to users reporting that things were "broken" as they then saw an immediate response.
The code you need will be placed in the HTML of the topic. Just insert it somewhere in the Head area.
<meta HTTP-EQUIV=refresh CONTENT="3;URL=File_Name.pdf">
Of course you will want to adjust it to suit your own needs. For example, the line above is configured for a 3 second delay. You may want a shorter (or longer) delay. And you would adjust File_Name.pdf to reflect the path and file name of the PDF (or other file) you are linking to.
Hope this helps... Rick
Helpful and Handy Links
It works PERFECTLY!!!! Thank you so much!