Other options than the VBA script are the pay for "Save As PDF" fancy plugin that is referred to somewhere in those instructions. ![]() I don't know if you can export the certificate and then save a copy in the trusted publisher location, because I didn't try that. You can see which security certificate is in which location using Internet Explorer/Internet Options/Content/Certificates as well - a copy of your certificate should be in Trusted Publishers as well as in the Personal folder. Once you authorize yourself as a trusted publisher by checking yes to the security warning, you should be able to go to Options/Trust Center/Trusted Publishers and see your security certificate listed. The settings in Options/Trust Center/Macro Settings should have a check mark next to "Notifications for digitally signed macros - all other macros disabled" and everything else on that set of options unchecked. But it did do that after a few tries.ĭid you make sure the macro was still signed? - the procedure of going to Tools in the VBA editor and signing it with your self-signed certificate has to be repeated if you make even the slightest change in the VBA script.Īlso the whole thing has to be saved and outlook 2013 closed and reopened, with its security settings back on, and the VBA script signed, to get the warning and the option to trust your macro. I also had a lot of trouble getting Outlook to finally display its warning that there was an unauthorized macro (which it identified as my own ) and ask whether to trust it anyway. But when you restore the security settings, and maybe reboot, opening outlook 2013 will sooner or later give a warning asking you if you should trust the signer of the certificate created, and then click "yes" to have it make you a "trusted publisher" and the VBA script should thenceforth run with normal security settings. You may have to at first turn off macro checking for signed certificates in the security options accessible in Outlook to run the macro and see that it works correctly - SelfCert.exe does not result in the certificate being immediately recognized as trusted. (The instructions are for Word 14 - it works fine with Word 15)Īlso, find the SelfCert.exe file (typically somewhere in the Word 15.0 directories) to create a self-signed certificate, so you can then sign the VBA macro you create following the instructions. Word 2013) Macros to the list of "references" for the VBA script, using the Tools options. To use this, you should not need any version of Acrobat installed at all!Ī key thing you might miss is to be sure to add in Microsoft Word 15.0 (i.e. The instructions at that site include installing an icon on the quick access ribbon so you can simply click and get a pdf. The macro invisibly uses Word 2013 to produce the pdf of the Outlook 2013 item, and it keeps all the url links intact in doing so. It is to use the free VBA script available as "saveaspdf" at. I did find a different workaround that produces the pdfs from Outlook 2013 with one click, with urls retained - but not attachmenets. The method I previously suggested does not do as well as I thought in keeping url links intact, which is true also of the Adobe PDF printer. It might also be worth putting a post in the desired features sub-forum though this is not really a feature, but something that needs repair. In the meantime, you will have to wait to see if one of the staff comes in with a response. When you start going back 2 or more versions, most of the fixes are for security updates and nothing more. ![]() For the prior version they typically try to fix such things. Usually there is a fair delay on Adobe fixing issues like you have mentioned. So without knowing more about Nuance, I can not give a fair comparison. ![]() Looking at the Nuance site, it does look like a nice product and supposedly interacts with WORD well. If Nuance adds those other features then you have a valid point (and again, I do not know what Nuance can do).Īcrobat is not a cheap product, but a lot of the cost goes into the extras that Acrobat offers and most other programs do not. ![]() Again, unless Nuance is able to add the additional functionality that PDF Maker does, then your comparison of Nuance does it and Acrobat does not is not a valid comparison. So PDF Maker is not the basic mechanism for creating PDFs, printing to the Adobe PDF printer is. If you just want a PDF from WORD, then why buy anything else since the MS plugin (or maybe it is standard now) will create the PDF. Those options often require more details to work properly with a product like WORD. PDF Maker is there to offer additional options, including links and such. The basic creation of a PDF from any product with Acrobat is to print to the Adobe PDF printer. But if you can print to the Adobe PDF printer from WORD and the same result is obtained with Nuance, then Adobe has not failed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |