PDFCreator is also open source, unlike Distiller which is costly. Trouble is, PDFCreator is one of the few PDF drivers that is possible to automate under program control (as far as I know Adobe don't provide such support for Distiller, although I believe it is possible). I mention this because I suspect that there is nothing at all wrong with your code, and that you may simply have to live with some inconsistencies in output to PDFCreator, inconsistencies which might not be there if you were using the Adobe Acrobat Distiller, say, to capture to PDF. Access reports have been faithfully reproduced, although as I have said I am not using automation to generate them. I find that in some cases it is not consistent about colour processing, for example of charts pasted into Word reports from Excel, which show in colour on Word's print preview but print in monochrome on the PDFCreator. I use PDFCreator routinely to route printed output from Access, Excel and Word to PDF, though not via automation (just using it as a normal printer). pdfcreator.exe /ManagePrintJobs 'C:\filea.pdf' 'C:\fileb.pdf' 'C:\filec.pdf' PDFCreator-cli. After that, all print jobs are converted automatically. This is useful when using auto-save as PDFCreator will keep all print jobs waiting until you manually continue the conversion. ' Set Application.Printer = Application.Printers("PDFCreator") 'Call to set printer to PDFCreator PDFCreator will start with the list of print jobs opened. 'Determine if need to print out cover sheet and Table of Contents Shell "taskkill /IM /T PDFCreator.exe", vbHide If pdfjob.cStart("/NoProcessingAtStartup") = False Then Set Application.Printer = Application.Printers("PDFCreator") 'Call to print to PDF Creator 'If option is print to PDF set default printer to PDFCreator and start PDFCreator
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |