Application.Followhyperlink

[April]

Sometimes I think I must just like banging my head against the wall?!

After over a week of trying to create a .pdf from several Word .docs in
Access VBA, I thought I was ready for Client testing. Then I loaded the
application onto their machine and something soooo simple that works on my
machine doesn't work on theirs.

All I'm trying to do is :
Application.FollowHyperlink strInput, , True
(where strInput is the path and file name of a .pdf file).

I can manually go to that directory and double click on the .pdf and opens
up the Adobe Acrobat Reader with the file just fine. I checked by file type
associations anyway, and all was correct. When I do it from the Access
application, I can see that it seems to flash open the Reader (or something -
too fast to tell), but instantly closes. I saw a post on this in my search
before posting this one from back on 9/7/2006 "Launching Acrobat" from
"Angus", but his resolution was essentially to check for every possible
version of the Reader and doing a Shell based on this check (but obviously
not opening the specific file). I'm not too keen on this as with the next
version of the Reader, it will stop working again - besides, I would like the
file to open. I tried it with a .doc version of the .pdf file and it opened
Word and the necessary file just fine (so I know its not a file system
permission thing), but not Adobe and the .pdf file?!

Very frustrating, if anyone has any suggestions.
Thanks,
April

 

[Dirk Goldgar]

In

Sometimes I think I must just like banging my head against the wall?!

After over a week of trying to create a .pdf from several Word .docs
in Access VBA, I thought I was ready for Client testing. Then I
loaded the application onto their machine and something soooo simple
that works on my machine doesn't work on theirs.

All I'm trying to do is :
Application.FollowHyperlink strInput, , True
(where strInput is the path and file name of a .pdf file).

I can manually go to that directory and double click on the .pdf and
opens up the Adobe Acrobat Reader with the file just fine. I checked
by file type associations anyway, and all was correct. When I do it
from the Access application, I can see that it seems to flash open
the Reader (or something - too fast to tell), but instantly closes.
I saw a post on this in my search before posting this one from back
on 9/7/2006 "Launching Acrobat" from "Angus", but his resolution was
essentially to check for every possible version of the Reader and
doing a Shell based on this check (but obviously not opening the
specific file). I'm not too keen on this as with the next version of
the Reader, it will stop working again - besides, I would like the
file to open. I tried it with a .doc version of the .pdf file and it
opened Word and the necessary file just fine (so I know its not a
file system permission thing), but not Adobe and the .pdf file?!

Very frustrating, if anyone has any suggestions.

I could be wrong, but I vaguely recall that there was a problem with the
first release of Adobe Reader version 7. Make sure that your client has
the latest version of Reader installed. I have 7.0.9 now, and even that
may not be the latest version.

 

[Ken Snell \(MVP\)]

I have 7.0.9 now, and even that may not be the latest version.

Nope, it's not. I have version 8.1.0 at this time....

 

[Alex Dybenko]

Hi,
try to use shellexecute API:
http://maug.pointltd.com/access/Queries/TipDetail.asp?TipID=5

--
Best regards,
___________
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com

 

[Pete]

Acrobat has a bad habit of taking taking over as the default file open and
then it won't open the pdf correctly. Started happening to me with acrobat
7 and continues with all the updates installed. Shell to reader and feed
the file name will cure the problem and prevent acrobat from taking over and
crashing after you have used it. Might be something else but this cured my
problem which sounds exactly like yours. Thier is a FAQ about making reader
the default on Adobe.com but everytime I open acrobat it changes it back.
Pete

 

[Alex Dybenko]

hi,
yes, agree with this, opening PDF worked fine at me using shellexecute, but
printing - no, so I had to use DDE(!) to print using acrobat

--
Best regards,
___________
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com