Convert Reports to PDF using a Library

  • Thread starter Thread starter Lamar
  • Start date Start date
L

Lamar

For a long time I have been using ACG Soft MS Developer Tools. I use the
PDF and Mail Class Library. It has work great me when we were using MS
Access 97 and Acrobat 5.0.

Now we are upgraded to MS 2003 and Acrobat 9.0. The ACG software is no
longer working. So I can someone give me a suggestion where I can buy a
Library or something to has the capability to allow me to "code' the
following:

Convert (Print) a report in Access to PDF
Name the PDF document and save the PDF in a chosen file folder

Have all this done without user intervention. What is happens I printing
one report after the other. I do not want the user to have to select the
printer, name the file, or use where to save it.

I want to do all this in the form coding. ACG Soft allow me to do this but
I need some developer software that works with MS Access 2003 and Acrobat 9.0
Any help is greatly appreciated.
 
I have VBA code to automate this process, tested with Acrobat versions 5
through 8, and soon to be tested with version 9. It works by setting
registry values that Acrobat reads when creating a pdf. Acrobat
documentation is pretty much nonexistent, but until they change these
registry settings, this approach has the advantage of being purely VBA
without any external dependencies. Let me know if you'd like a copy since
the code is too big to post here.
 
Yes, I would like a copy. What is the best way to get it? I did not want
to give my email address for everyone to see. Thanks.
 
Douglas,

The ReportToPDF works well but one problem is it makes the PDF document so
much larger (Over 100 KB vs 14 KB) than when you use the Acrobat print
driver. Any suggestions. Do you think there is modifications to the coding
that would allow to use the Acrobat print driver. I have Acrobat so the
issue is being able to make the PDF documents smaller.
 
As far as I'm aware, there are licensing issues with the Acrobat print
driver that Stephen didn't want to get involved with. There are absolutely
no licensing issues with what Stephen used, which is why he went that way.

I seem to recall Stephen saying something at one time that some of the size
issues can be font-related: that certain fonts end up getting embedded into
the document, thereby increasing its size. Perhaps you can try different
fonts and see whether it makes a difference.

Even if it were possible to modify the coding, it's not going to happen any
time soon: Stephen is currently enjoying a nine month sabbatical.
 
You can guess my email from the slightly mangled one given in my posting.
Drop the 'hideme' portion.

The code has my own error-handling and other dependencies, so you'll have to
do some cleanup to use it. But the code itself is well-commented. Since the
earlier post, I've added Acrobat 9 support, so it works with Acrobat
versions from 5-9.
 
Paul Shapiro said:
I have VBA code to automate this process, tested with Acrobat versions 5
through 8, and soon to be tested with version 9. It works by setting
registry values that Acrobat reads when creating a pdf. Acrobat
documentation is pretty much nonexistent, but until they change these
registry settings, this approach has the advantage of being purely VBA
without any external dependencies. Let me know if you'd like a copy since
the code is too big to post here.
Click to expand...

If you like I'd be happy to have that file as a web page or
downloadable from my website. With full credit to you of course.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
Thanks Tony. That would be great. I've much appreciated the services you and
others provide to the community.

I sent the code to the original requester last night. I'll wait a couple of
days to see if he has issues with it and then send it on to you. I had
removed the code that automates pdf production from Word documents, since he
didn't need that feature and there were too many references to clean up to
get it to compile. If you're going to post a copy, I'll try to add that back
to the sample code.
 
Back
Top