By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,686 Members | 2,392 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,686 IT Pros & Developers. It's quick & easy.

MS Access Report to PDF

P: n/a
Hello All,

I have been doing quite a bit of research in this group and have not
been able to find the answer that I am looking for.

Here is my issue. We currently have Adobe Acrobat v5 installed on our
system (under Windows 2000 Professional). Currently, we are using MS
Access 2000. Early next year we will be moving to Windows XP (probably
converting to MS Access XP as well) and have been told that Adobe
Acrobat v6 is to be installed as the new standard. Oh yeah - they have
also told us NO to having Acrobat v5 installed. This means that we will
no longer have access to PDF Writer, which we currently utilise to
generate PDF documents from reports. PDF Distiller apparently is
replaced with PDF Print (if memory serves me well). I have tried
working with PDF Distiller and have not had any success, very messy,
unlike PDF Writer.

My question for the group is; does any know how I am will be able to
generate PDF documents from MS Access 2000/XP without PDF writer using
Adobe Acrobat v6 PDF print? Oh yeah - third party tools (other then MS
Office and Adobe Acrobat v6 standards) are a NO NO, for example Win2PDF
etc.

Does anyone have any suggestions? Has anyone been able to PDF Print to
work from VBA?

Please note: I'd rather not get into creating SNP (snapshot views)
since we send our documents externally at times).

Thank-you all, in advance, for your time and attention to this
matter...

Regards,
Dave

Nov 13 '05 #1
Share this Question
Share on Google+
12 Replies


P: n/a
We have a full version of Acrobat. I used something else simpler than
Acrobat to program. It is pdf995. On their site, there are examples for
developers in VBA.

http://www.freeware995.com/misc/vbacode.txt

"DGB @ Sun" <Da***************@SunLife.com> wrote in message
news:11**********************@g47g2000cwa.googlegr oups.com...
Hello All,

I have been doing quite a bit of research in this group and have not
been able to find the answer that I am looking for.

Here is my issue. We currently have Adobe Acrobat v5 installed on our
system (under Windows 2000 Professional). Currently, we are using MS
Access 2000. Early next year we will be moving to Windows XP (probably
converting to MS Access XP as well) and have been told that Adobe
Acrobat v6 is to be installed as the new standard. Oh yeah - they have
also told us NO to having Acrobat v5 installed. This means that we will
no longer have access to PDF Writer, which we currently utilise to
generate PDF documents from reports. PDF Distiller apparently is
replaced with PDF Print (if memory serves me well). I have tried
working with PDF Distiller and have not had any success, very messy,
unlike PDF Writer.

My question for the group is; does any know how I am will be able to
generate PDF documents from MS Access 2000/XP without PDF writer using
Adobe Acrobat v6 PDF print? Oh yeah - third party tools (other then MS
Office and Adobe Acrobat v6 standards) are a NO NO, for example Win2PDF
etc.

Does anyone have any suggestions? Has anyone been able to PDF Print to
work from VBA?

Please note: I'd rather not get into creating SNP (snapshot views)
since we send our documents externally at times).

Thank-you all, in advance, for your time and attention to this
matter...

Regards,
Dave

Nov 13 '05 #2

P: n/a
"Saintor" <sa******@REMOVETHIShotmail.com> wrote in
news:hC********************@weber.videotron.net:
We have a full version of Acrobat. I used something else simpler
than Acrobat to program. It is pdf995. On their site, there are
examples for developers in VBA.

http://www.freeware995.com/misc/vbacode.txt


Wow, that's ugly code.

I'd suggest replacing the hardwired All Users reference with the
environment variable ALLUSERSPROFILE, for one.

The code also reminds me of PDF995's poor behavior in insisting that
install itself in the root of your C: drive. That's *extremely* bad
design for an application designed to run under any NT-based version
of Windows other than NT 4 itself, since by default, the root of C:
is read-only accessible to users.

I use PPF995, but this one thing is very, very poorly implemented.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #3

P: n/a
I too have struggled with the automated conversion of a report to PDF.
I finally ended up automating snapshot outputs and then converting
those to PDF...

Nov 13 '05 #4

P: n/a
Even if it is ugly (or may be not), if it works and is reliable...who cares?

..
Wow, that's ugly code.

I'd suggest replacing the hardwired All Users reference with the
environment variable ALLUSERSPROFILE, for one.

The code also reminds me of PDF995's poor behavior in insisting that
install itself in the root of your C: drive. That's *extremely* bad
design for an application designed to run under any NT-based version
of Windows other than NT 4 itself, since by default, the root of C:
is read-only accessible to users.

I use PPF995, but this one thing is very, very poorly implemented.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

Nov 13 '05 #5

P: n/a
"Saintor" <sa******@REMOVETHIShotmail.com> wrote in
news:yQ*******************@wagner.videotron.net:
Even if it is ugly (or may be not), if it works and is
reliable...who cares?


Ugliness in code generally indicates to me that:

1. there are design problems that necessitate the ugliness, AND

2. it's a maintenance problem, particularly with hardwired paths.

When I see ugly code provided by a 3rd party, it makes me think
"Hmm, looks like this was not written by someone who knows too much
about conventions for programming in this particular language." and
that makes me suspect the code overall.

It may very well work.

It may very well be the best code that can be used to accomplish the
task.

And I might very well use it.

But I still would feel uncomfortable about it.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #6

P: n/a
Hi Nick,

Thank you very much for your input...
I looked into this option as well but was unclear on how to convert SNP
to PDF. Do you have any suggestions and/or code?

Thanks again Nick...

Regards,
Dave

Nov 13 '05 #7

P: n/a
Hi David and Saintor,

Thank-you both for your input...
Saintor, I will look into this code more carefully. Although I am very
interested in Nick's suggestion, i.e. the conversion from SNP to PDF.
Any case, I open to all suggestions. Fact of the matter all, what was
Adobe thinking? You would think a company would want to retain
functionality that promotes their product ?!? Such is life...

Dave

Nov 13 '05 #8

P: n/a

Thank you very much for your input...
I looked into this option as well but was unclear on how to convert SNP
to PDF. Do you have any suggestions and/or code?


Once Acrobat is installed, I believe you can just right-click the
Snapshot file and choose 'Convert to PDF.'

I didn't have any luck automating this process with VBA.

Nov 13 '05 #9

P: n/a
Hi Nick,

Thanks for your quick response...
I, unfortunately, don't get the option 'Convert to PDF' when I right
click on the file. In any case, I would have to implement something
that converts the file through code.

Thanks for your time...

Regards,
Dave

Nov 13 '05 #10

P: n/a
I have a solution I will be posting this weekend hopefully. It converts
Reports or Snapshots to PDF documents. The Snapshot file is comprised of
Enhanced Metafiles(EMF), one for each page of the report. Each EMF is
comprised of records that render the elements of the output page.
I purchased a developer's license for a third party PDF library. It has the
capability to convert the records of an EMF file to their PDf counterparts.
This is a one to one mapping of Metafile to PDF records. The resultant PDF
document is as fully editable as any normal PDF doc. The developer of the
library has kindly consented to allow me to redistribute his library in my
Freeware solution.

This solution is comprised of an MDE file and the PDF library DLL. It's a
standard Windows DLL, not an ActiveX DLL so no registration is required. No
printer driver is required therefore the solution will work even on desktops
locked down by corporate IT.

If you want, send me an Email and I'll forward you a Beta for you test. I
have tested it on more than 40 reports where it has converted perfectly but
it's time to broaden the tests.
My Email address is:
my*********@mylastname.com

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.
"DGB @ Sun" <Da***************@SunLife.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...
Hi Nick,

Thanks for your quick response...
I, unfortunately, don't get the option 'Convert to PDF' when I right
click on the file. In any case, I would have to implement something
that converts the file through code.

Thanks for your time...

Regards,
Dave

Nov 13 '05 #11

P: n/a
What about CutePDF Writer - http://www.cutepdf.com/ a shareware utility
(with a freeware version) that installs itself to look like an optional
printer?

On 14 Oct 2005 12:30:47 -0700, "DGB @ Sun" <Da***************@SunLife.com>
wrote:
Hello All,

I have been doing quite a bit of research in this group and have not
been able to find the answer that I am looking for.

Here is my issue. We currently have Adobe Acrobat v5 installed on our
system (under Windows 2000 Professional). Currently, we are using MS
Access 2000. Early next year we will be moving to Windows XP (probably
converting to MS Access XP as well) and have been told that Adobe
Acrobat v6 is to be installed as the new standard. Oh yeah - they have
also told us NO to having Acrobat v5 installed. This means that we will
no longer have access to PDF Writer, which we currently utilise to
generate PDF documents from reports. PDF Distiller apparently is
replaced with PDF Print (if memory serves me well). I have tried
working with PDF Distiller and have not had any success, very messy,
unlike PDF Writer.

My question for the group is; does any know how I am will be able to
generate PDF documents from MS Access 2000/XP without PDF writer using
Adobe Acrobat v6 PDF print? Oh yeah - third party tools (other then MS
Office and Adobe Acrobat v6 standards) are a NO NO, for example Win2PDF
etc.

Does anyone have any suggestions? Has anyone been able to PDF Print to
work from VBA?

Please note: I'd rather not get into creating SNP (snapshot views)
since we send our documents externally at times).

Thank-you all, in advance, for your time and attention to this
matter...

Regards,
Dave

Nov 18 '05 #12

P: n/a
There are some problems printing to it programmatically: I don't believe
it's possible without some user interaction. However, PDF995
http://www.pdf995.com does support automation.

Of course, David did say no third part products.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

<lo*****@internet.com> wrote in message
news:gs********************************@4ax.com...
What about CutePDF Writer - http://www.cutepdf.com/ a shareware utility
(with a freeware version) that installs itself to look like an optional
printer?

On 14 Oct 2005 12:30:47 -0700, "DGB @ Sun" <Da***************@SunLife.com>
wrote:
Hello All,

I have been doing quite a bit of research in this group and have not
been able to find the answer that I am looking for.

Here is my issue. We currently have Adobe Acrobat v5 installed on our
system (under Windows 2000 Professional). Currently, we are using MS
Access 2000. Early next year we will be moving to Windows XP (probably
converting to MS Access XP as well) and have been told that Adobe
Acrobat v6 is to be installed as the new standard. Oh yeah - they have
also told us NO to having Acrobat v5 installed. This means that we will
no longer have access to PDF Writer, which we currently utilise to
generate PDF documents from reports. PDF Distiller apparently is
replaced with PDF Print (if memory serves me well). I have tried
working with PDF Distiller and have not had any success, very messy,
unlike PDF Writer.

My question for the group is; does any know how I am will be able to
generate PDF documents from MS Access 2000/XP without PDF writer using
Adobe Acrobat v6 PDF print? Oh yeah - third party tools (other then MS
Office and Adobe Acrobat v6 standards) are a NO NO, for example Win2PDF
etc.

Does anyone have any suggestions? Has anyone been able to PDF Print to
work from VBA?

Please note: I'd rather not get into creating SNP (snapshot views)
since we send our documents externally at times).

Thank-you all, in advance, for your time and attention to this
matter...

Regards,
Dave

Nov 18 '05 #13

This discussion thread is closed

Replies have been disabled for this discussion.