Problems with hyperlinks when creating Adobe pdf from a report

[jf]

When I try to create an Adobe pdf from a report, the full hyperlink address
is not recognized. I have several text boxes that are hyperlinks in the
report, but when I create the pdf, the entire address isn't selected.

For example:
www.microsoft.com/office/
community/en-us/

In the pdf, if I clicked on the above hyperlink, only
"www.microsoft.com/office/" is selected and i get an error stating that the
address is not valid. In the pdf, the entire hyperlink appears normal, but
only the first line of the address is "clickable".

 

[James A. Fortune]

When I try to create an Adobe pdf from a report, the full hyperlink address
is not recognized. I have several text boxes that are hyperlinks in the
report, but when I create the pdf, the entire address isn't selected.

For example:
www.microsoft.com/office/
community/en-us/

In the pdf, if I clicked on the above hyperlink, only
"www.microsoft.com/office/" is selected and i get an error stating that the
address is not valid. In the pdf, the entire hyperlink appears normal, but
only the first line of the address is "clickable".

Until Microsoft becomes aware of the problem and considers whether or
not to fix it, you should consider using PDF editing software to fix the
multiline links after the PDF file is created. If you have control over
the PDF creation process, then pages 907-909 of the PDF Reference,
version 1.7 by Adobe show how to set up the additional link annotations
necessary to have line-wrapped links work as expected. I suspect that
checking for that situation and making the appropriate changes is not
trivial so I can't blame Microsoft for not opening that can of worms.
Is there a way to put the links at the beginning of their own line so
that there is less chance of them being line-wrapped?

James A. Fortune
(e-mail address removed)

 

[jf]

James, thanks for your reply. I looked at the reference you provided.
However, I am not sure how to do that when I am exporting from an Access
report into an Adobe pdf. Also, I have several database users that will be
exporting the report and I can't expect them to fix the links everytime.

I cannot put the hyperlinks on their own lines due to the requirements of
the report.

 

[James A. Fortune]

James, thanks for your reply. I looked at the reference you provided.
However, I am not sure how to do that when I am exporting from an Access
report into an Adobe pdf. Also, I have several database users that will be
exporting the report and I can't expect them to fix the links everytime.

I cannot put the hyperlinks on their own lines due to the requirements of
the report.

The reference is only useful if you are rolling your own PDF using VBA
or using other PDF creation software without using the PDF output Add-in
provided by Microsoft for Access 2007. In that case, the information in
the reference can be used to adjust how the hyperlink is created. I
often create PDF reports directly from Access without using the Add-in,
but that technique can get complicated quickly if the report contains
multiple levels of groups. Also, check to see if Stephen Lebans'
software for creating PDF reports from earlier versions of Access
succeeds with multiline hyperlinks or allows you to manipulate the PDF
commands for creating hyperlinks. You're running out of options, but
since having hyperlinks in PDF documents are desirable, I'll do some low
priority wading into multiline hyperlinks to see exactly how complicated
it is. If your report is somewhat complex and Stephen's solution
doesn't allow the creation of multiline hyperlinks, then you'll be stuck
with using the Add-in anyway even if creating multiline hyperlinks from
VBA or from using other PDF creation software turns out to feasible.
Stephen's use of the snapshot version of the report to create the PDF
turns out to be a nice compromise since reproducing report layout logic
from the report contents alone can get messy. I don't use the snapshot
so my implementation of PDF creation through VBA is limited to reports
that are not too intricate as far as groups are concerned, although I
suppose such intricacies are only a matter of extra effort. One of the
reasons I have for creating PDF files using VBA is to be able to have
Visio style capabilities so that I can convert general notes into an
electronic format. Even the Access 2007 Add-in does not change that
purpose. The code I use has the benefits cited for Stephen's software,
such as not needing to print to a PDF writer, plus it doesn't even need
the DLL files. It allows for much more varied output than from Access
reports, but requires much more work to implement.

James A. Fortune
(e-mail address removed)