Adobe provides everything you need to design and deliver exceptional digital experiences. View a complete list of our products and services. I agree 100% Adobe reader has grown too big and too unsafe to use. I use Foxxit reader and love it. And now I don't have all the issues with slow running and bloat. TheINQUIRER publishes daily news, reviews on the latest gadgets and devices, and INQdepth articles for tech buffs and hobbyists. Other editions: Adobe Reader for Mac OS X (Intel) Adobe Reader for Linux; Adobe Reader for Mac OS X (PPC).

Adobe Acrobat and VBA – An Introduction. Update: Please visit the same post on my business site.

The comments are closed here, so if you want to comment, you have to head over to http: //khkonsulting. Here is another topic that comes up every now and then: How can I “talk” to Adobe Acrobat from e. MS Excel via VBA? I’ll try to give an introduction into that subject in this document. I will only discuss the basics, but I’m open for suggestions about what part to discuss next. So keep the comments coming.

More after the jump. I do not program in VBA or VB.

All I know about VB is from googling a few things and looking at sample code. It does help that I’ve programmed in many (make that a capital . I only use the samples to demonstrate general methods. It’s up to you to fill in all the missing details (e. Before you read any further, click on this link and take a look at what they have available. There are (at least) two documents that are required reading if you want to use Acrobat from within your VBA code: If you want to utilize the VB/Java. Script bridge, you also should read the Java.

Script related documents: All of these documents can also be accessed via Adobe’s online documentation system. In order to find the documents I’ve listed above, you need to expand the tree on the left side of the window for the “Java. Script” and “Acrobat Interapplication Communication” nodes. There is always more than one way. Frameless Shower Door Installation Videos For Wedi. One is more direct than the other, but both require the same mechanism to get things started. The latter case still requires that your program first establishes a connection to Acrobat via IAC.

Let’s get the party started. As I mentioned before, regardless of how we want to remote control Adobe Acrobat from VB, we need to establish a connection to it’s COM object (or OLE server). You may have noticed that I always talk about “Adobe Acrobat”, and not the “Adobe Reader”. What I’m presenting here is valid for the Adobe Acrobat, Reader only supports a small subset of features. To learn more about what the differences are, see the IAC Developer Guide.

For the purpose of this document, I will use MS Excel 2. Adobe Acrobat 9 Pro. As long as you have a version of Acrobat that is compatible with the version of VBA that you are using, you should be able to follow along without any problems. Preparing MS Excel 2. When you install Office 2.

Excel 2. 00. 7, make sure that you select the Visual Basic Editor component, otherwise you will not be able to write VBA code. This is different than all the versions up to 2. Once installed, you need to add the “Developer” tab to the ribbon.

This is done on the Excel Options dialog, under the Popular category: Once that is done, you should see the “Developer” tab as part of the ribbon: Our First Button. Open a new document and select the Developer tab. Then go to the Insert control and place a button on your document. This will pop up the “Assign Macro” dialog, just click on the “Add” button, which will bring up the VBA editor. Nothing special so far.

Before we can use any of Acrobat’s functionality, we need to make sure that VBA knows about the Acrobat objects. On the VBA dialog, select the “Tools> References” menu item. On the dialog that pops up, make sure that the TLB for your version of Acrobat is selected.

This is what it looks like for my system: Now we can add code that references the Acrobat objects to our button handler. Of course, before we do that, we need to decide what our button is actually supposed to trigger. Let’s start with something simple – let’s combine two PDF documents and save the result as a new document. I’ll present the whole program first, and will then explain the different parts. Sub Button. 1. When prompted for a filename and a filetype, select the type of “Excel Macro- Enabled Workbook” – otherwise the program you just added will get stripped out of the file.

Make sure that there are two files named Part. Part. 2. pdf in the c: \temp directory. Click the button and enjoy. Open that in Acrobat, and verify that it indeed contains the results of concatenating the two source files. So, how does it work? The whole program is in a button handler. Sub Button. 1. If you look through the documentation, you’ll see that there are a number of things that can be done on the application level (e.

The next two lines declare two objects of type Acrobat. CAcro. PDDoc – these reflect the two documents that we need to open. There are two different document types available in the OLE part of IAC: The AVDoc and the PDDoc.

An AVDoc is one that gets opened in Acrobat’s user interface, the user can navigate through it’s pages, and do anything that you can do with a PDF document when you double- click on it to open it in Acrobat. A PDDoc on the other hand gets opened in the background.

Acrobat still has access to it, and can manipulate it, but the user does not see it. This is useful if a program should quietly do it’s work without showing the user what’s going on. Every AVDoc has a PDDoc behind the scenes, and that object can be retrieved via the AVDoc. Get. PDDoc method. A PDDoc only has an associated AVDoc if it is actually shown in Acrobat, however, we cannot retrieve that AVDoc object from within the PDDoc. This sounds complicated, but once you get more familiar with how these things are used, it becomes second nature. We also need an integer object to store the number of pages in the first document.

Nothing special here. In order to merge files, we need access to both the source files, so we have to call the Open() method on both these objects. The key to success is to specify the whole path name, directory and filename. Because we want to insert the pages after the last page of the first document, we need to find out how many pages we have in that document. The Get. Num. Pages() method does return that information.

This is also, where it becomes a bit tricky: Acrobat starts to count the pages in a PDF document at zero. So, if we want to insert the pages after the first page in the document, we need to insert after page number zero. If we want to insert after the second page, we need to insert after page number one. Again, this is a bit confusing, but after a while it gets easier. The parameters of the Insert.

Pages method are described in the Interapplication Communication API Reference document: Insert. Pages. Now we only have to save the document, do some cleanup and exit our program:    If Part. Document. Save(PDSave.