This post may not be directly on topic, but some forum members might find my experience useful.
Quote:
this does require you and your end users to have Acobat Reader installed.
Coincident with the last few releases of Acrobat Reader, there seems to be some compatibility issues with
older PDF files and these new versions of Acrobat Reader.
I'm prepared to accept that this might well be the result of my over-active imagination
but increasingly, clients have reported that older PDF documents (particularly those based on versions of PDF earlier than version 5) do not sit happily with current versions of Reader.
My solution to this is not new, but it might be worth repeating here in case others are having similar challenges.
1. These days there are more ways of creating PDF files than by using Adobe Acrobat. For example several stand-alone applications, and a few word processing packages support saving or publishing files to PDF. I use WordPerfect, and publish my files to PDF version 5.0.
2. Following recommendations from other Opus users, I downloaded a copy of PDF2EXE (free version) and use that to convert all the PDF files that I want to use in Opus, to standalone EXE files. These files have their own PDF reader, and are completely independent of Acrobat Reader.
During the conversion, I have the opportunity of setting many parameters that control how the resulting EXE files can be used. (Many more parameters are available if the pro version of PDF2EXE is used.) I set these parameters so that users can both view and print the EXE file.
3. When I need to incorporate a PDF file into an Opus pub, I use the Launch File action. Reminder: to make sure that Opus can find these files, place these files in the <SYSTEM_PUBLICATION_DIR>
While it's early days, since I started using PDF2EXE (and made retrospective conversions of PDF files) I have received no complaints about PDF incompatibilities.