In both cases Adobe Acrobat 9 is installed. "adx_king" schrieb im Newsbeitrag have now migrated the VBA application to Office 2010 (64 bit) andĪlthough the template is still referenced to the Adobe Reader control, theĪcroPDF object is not available in the toolbox. They offer SDK or something similar to use it in the 64-bit environment. I for myself prefer the Foxit PDF reader as it has a smaller footprint and is quite stable without the overhead and of the Acrobat reader. There in the meantime are tons of other PDF readers out in the wild. This one then can run in the 32-bit environment,īut you can't interact with this one over it's object model. If it's only to open a PDF file you could use Application.FollowHyperlink to open the PDF file with it's registered application. You will run in other problems as soon as you are using the programming environment with API calls and other 3rd party ActiveX controls that aren't available I heavily recommend to follow the recommendation of MS and install Office 2010 in the 32-bit version. And to easily edit and convert your PDFs into file formats like Excel and Word, try out PDF editor and converter Acrobat Pro. View, sign, collaborate on and annotate PDF files with our free Acrobat Reader software. Is no way to get into this environment programmatically.Īs there is no 64-bit version of Acrobat you will not be able to use it in Office 64-bit version. Acrobat Adobe Acrobat Reader The best PDF viewer just got better. But your Office is running outside and there 32-bit DLL can only be run in the WOW64, the 32-bit environment of Windows 7. If you are using Office in the 64-bit version you can only only 64-bit DLLs. You can't run a 32-bit DLL out of a 64-bit application.
0 kommentar(er)
