11-29-2017 08:15 AM
Hello
Can DIAdem support Adobes APToolkit?
I would like to script some Adobe features like merging Pdf files and printing image files to PDF
Thanks
11-30-2017 04:27 PM
Are you trying to integrate Adobe ActivePDF Toolkit ? Is there a reason you're interested in ActivePDF versus normal PDFs?
Looking at DIAdem included functionality, there are two ways to merge PDFs built into DIAdem that may be helpful.
If the APToolkit operates on ActiveX functionality, you could theoretically call ActiveX to control the Adobe program. Neither Adobe nor VBScript are National Instruments products, so I doubt there are any NI-exclusive support resources for this.
I included some external resources below that may be of help.
Best,
Chris D. | Applications Engineer | National Instruments
12-04-2017 08:32 AM
Chris thanks for the response
I would like to be able to use VBS to convert image files to PDF's programmatically and then merge them together.
I have spent a little time researching this and was able to find the following function call
Set pdfTemp = CreateObject("APToolkit.Object")
How ever when I try to create an APToolkit object I get error stating;
ActiveX component can't create object APToolKit.Object
Thoughts?
12-05-2017 09:26 AM
Hi Tim,
The CreateObject() command is standard Microsoft VBScript. This works in a *.VBS file that you just double-click on in Windows Explorer or start with a batch file, thereby using the Windows VBScript Engine that installs with the operating system. So it has nothing to do with DIAdem or the specific DIAdem VBScript host per se. The CreateObject() command should work for all ActiveX servers or COM objects that are correctly registered with the operating system and share the same bitness as the calling application. Have you tried with both a 32bit and 64bit version of DIAdem? I'd actually suggest you try to connect to this "APToolkit.Object" with some application other than VBScript-- say LabVIEW or C++. If you can connect, then that suggests that this is either an ActiveX server or COM object that is correctly registered with the operating system on that computer.
By the way, the class name "Object" in the "Library.Class" string "APToolkit.Object" sounds suspicious to me. I haven't seen any other Class names of "Object" before. You might want to double check if there are any other Class names listed in the internet or other Help material for that toolkit.
Brad Turpin
DIAdem Product Support Engineer
National Instruments