By-pass dialog w/print to .pdf

[KenHigg]

I've searched on this and have come up with deadends. I'm using Acrobat 7 and I don't think it uses the writer but somehow uses the distiller. So I've tried the examples where you set writer stuff in the registry and nothing works.

All I need is to by-pass the where do you want to save it dialog and pass it when it print via code - Any fresh ideas -

 

[CyberLynx]

If what you are doing is converting your Reports to .pdf then perhaps try the class from Stephen Lebans which can be found here.

I use this module and the DLL's quite often and I personally think it works quite well. There are two DLL files which must accompany the Database but this is minor. The DLL's do not need to be registered to Windows either.

.

 

[KenHigg]

Thanks - I looked at that and tryed to stay a way because it looked complex. Seeing as how I'm at a dead-end otherwise I guess I'll give it a try -

 

[LPurvis]

I've had to "control" Adobe's PDF creation in the past, but it was with version 6 and it unquestionably had less than ideal control over the destination.
(It was able to be partly assigned - but I find the process Adobe places on us restrictive and unecessary). Hence folks often move created PDF files to where they want them to be afterwards. (The trick then is determining when Acrobat has finished the writing process).

By comparison Stephen Leban's methods are controlled, effective and free for all (well - except him I suppose, but that's part of the magnanamous gesture he's made in developing it. ;-).
He's updated it fairly recently - to include functionality such as merging distinct PDF files and so forth (which reminds me - I'm meant to be mailing him something about that... just a teeny bug but I doubt that's an issue).
I was surprised to find how important such functionality is to some users (merging files). But you know - who's to predict what's important to users at times.

I assume you're not using Access 2007 yet then? (With the PDF export option - with the MS Addin installed).

Cheers.

 

[KenHigg]

Nah, XP Pro and Office 2003. Basically I just want to push a button and have a report converted to .pdf and email it all in one step. The other option is print to pdf create and email and attach it. Not that big a deal in the current project but there is one coming up where it will be as there will be hundreds of these pdfs created during the course of a work day.

 

[LPurvis]

That's all fine really.
The only complexity (i.e. effort) in Stephen's code (apart, no doubt, from the C++ he's used in the DLL) are in his standard modules.
The implementation of the methods he's written is simple.
Just calling a couple of functions tops sees the PDFs created where you'd want them.

The only issue might be the distribution of the DLLs that power it (if you're not in a single location - and even then some IT depts might worry about external components being installed). AFAICR the 3rd party PDF DLL is a little over a meg, and his own supporting DLL is just a few K.
If distribution is an issue then it's either including them as part of an installer routine, downloading them from the web, or including them in your application (/BE) as BLOBs and extracting upon first use.
They don't require registering - merely locating in an appropriate (e.g. local) directory.

 

[CyberLynx]

Give it a try Ken, I think you will find that it's a lot easier to use than it appears and I believe you will like the results.

.