Acrobat Distiller, Excel, Adding a reference in VBA

I have a snippet of VBA to generate a PDF through Excel. I expected to see "Acrobat Distiller" in the references under the menu option Tools/References in the Visual Basic editor. It's not there. Can anyone help?

On the Macintosh, there is no OLE interface to Acrobat at all. The
Acrobat SDK describes the different Macintosh interfaces.
Aandi Inston

Similar Messages

? Office 2013 to support Excel 2003 (XLS) spreadsheets containing VBA CommandBars references

Thanks in advance for reading this and offering any wisdom you have! I am not an expert in any of the following, so apologies if off base.
The basic problem is: I need to use Excel 2013 to support Excel 2003 (XLS) spreadsheets containing VBA 'CommandBars' references which don't seem to work in Excel 2013. Details below.
Most of our users are still using older desktop windows PCs and Office 2003! We are beginning to upgrade to laptops running Windows 8.1 with Office 2013. Of course, we IT technical people are using the new laptops first. These new laptops are
64 bit.
Years ago, someone did a lot of development with spreadsheets here in Excel 2003 file formats that automates many activities and routines. Now we with the new laptops are having to support this development using new machines.
There is a basic compatibility issue that appears when first opening these Excel 2003 files that have VBA code that I'll detail below; I seem able to get by that problem.
The current problem appears to be that the existing Excel 2003 VBA code has many references to: "For Each bar In Application.CommandBars". As I've learned, the Application.CommandBars VBA functionality is focused on older MS Office versions' menu
commands, but "...Starting from Office 2007 the Fluent UI is used instead." In other words, because MS Office isn't menu-driven beginning with version 2007 (uses 'the ribbon'), it appears that these references to: "For Each bar In Application.CommandBars"
create a basic incompatibility to opening these spreadsheets in Office 2013.
For a spreadsheet, after I resolve the issue detailed below and save it, when I reopen it I encounter error "Compile error: can't find project or library."
For example, the following code snippet:
Private Sub Workbook_Open()
For Each bar In Application.CommandBars
bar.Enabled = False
Next
results in: "Compile error: can't find project or library."
(Sorry, can't include images yet, I am not a VERIFIED USER of this forum yet.)
I went into VBE's menu: Tools>References and check for anything marked MISSING, which I deselected. But I am still receiving this error.
I don't want to get into changing the code a lot to support both Excel 2003 and 2013 (I am no VBA expert, just a dabbler).
And Microsoft officially says that Office 2003 is incompatible with Windows 8 although Application.CommandBars seem to be somewhat supported in Office 2013 .
Are you aware of a quick VBA workaround to get by this?
•I could comment out the validations, commands for: "For Each bar In Application.CommandBars" but then the spreadsheet code probably won't work for users using Office 2003.
Alternatives would be:
•Installing Office 2003 on my Win 8.1 64 bit laptop anyway, in spite of MS's saying incompatible, since this thread discusses at least one person has been able to use Office 2003
•Keeping one older PC with Office 2003 on it for us to support the old Office 2003 code until everyone upgrades their systems
Thanks
Basic compatibility issue that seems solvable:
Opening these spreadsheets displays this error:
Compile error:
The code in this project must be updated for use on 64-bit systems.
Please review and update Declare statements and then mark them with the PtrSafe attribute.
This seems resolvable by going into the VBA code and just adding element 'PtrSafe' where functions are declared; in other words, replacing VBA code "Declare Function" with "Declare PtrSafe Function" seems to get by this.

Hi Allan_L,
Please try the methods that provided above. And this is the forum to discuss questions and feedback for Microsoft Excel, your issue is related to Excel DEV, if you have further question, I recommend you post the question to the MSDN forum for Excel
http://social.msdn.microsoft.com/Forums/en-US/home?forum=exceldev&filter=alltypes&sort=lastpostdesc
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Solved: "Error in loading DLL" adding vb Reference to Photoshop CS5.1 (CS5.5)

It took me a while to solve this so I thought I'd post the solution.
On two machines (one 32-bit the other 64-bit) running the new Phonoshop CS5.1 that ships with CS5.5, I had trouble adding a reference in vb (vba) to the Photoshop Object Library for scripting:
I would just get: Error in Loading DLL
It appears that on both machines, the CS5.5 installer incorectly referenced the dll which is called "ScriptingSupport.8li" (not exactly a .dll-looking name but anyway ;-)
The Adobe CS5.5 installer set the system registry to look for the file in:
C:\Program Files\Adobe\Adobe Photoshop CS5.1 (64 Bit)\Plug-ins\Automate
or
C:\Program Files\Adobe\Adobe Photoshop CS5.1\Plug-ins\Automate
but installed the file to:
C:\Program Files\Adobe\Adobe Photoshop CS5.1 (64 Bit)\Plug-ins\Extensions
or
C:\Program Files\Adobe\Adobe Photoshop CS5.1\Plug-ins\Extensions
I copied ScriptingSupport.8li from the Extensions folder to the Automate folder and it started working.
Hope this helps someone else. :-)
Tony

Yes, another user has the issue with windows "mandatory profiles", where rights are severely limited for users (french forum): http://forums.adobe.com/thread/948264

Unable to embedded xls files word doc with acrobat distiller 6

Hi,
I have a problem to convert a Microsoft Word docs with embedded excel(*.xls) to PDF using Adobe Distiller 6. The excel file will become an image file after conversion.
Please advise on what went wrong or is this a limititaion of Adobe Distiller 6.
Thank you in advance.
Regards,
Haikal

I suspect that what you are asking as nothing to do with Acrobat. For what you are doing, there is no need to use PDF Maker (unless you are looking for links or such). You do not have to use Distiller (unless you are taking about the Acrobat Distiller printer with AA5 and earlier), but simply print to the Adobe PDF printer (that automates the use of Distiller). In fact, Distiller can not handle DOC files, so I suspect you are using AA5. However, the end result will be based on whatever WORD sends to the printer, not how Acrobat converts it. If text is sent, then Acrobat will convert it accordingly. Sounds like WORD is sending the Excel file as a graphic. It may just be that is how WORD handles that OLE aspect of the embedding.
I am no expert on WORD (I use another package), but I really doubt that Acrobat is at fault. I would look at what WORD is doing. One way to do this is to print to a PS file (you can do this with the Adobe PDF printer using print-to-file. Open the PS file and you should find a graphic structure in the PS that represents the Excel file.

Xref table is missing when a pdf file is created with acrobat distiller 9.0.0

Hi
I created a pdf file with the new acrobat distiller 9.0.0 and i noticed that the xref table is missing in it.
Whereas the pdf files which created in older version (acrobat distiller 7.0.5) had the xref tables.
As i have written a perl script to open the pdf files (used a ready made module downloaded form cpan.org). The script works fine with all old pdf files but fails when it tries to open the pdf files created with distiller 9.0.0.
Could i know is any thing changed on acrobat distiller 9.0.0 ?
Thanks
Balaji.

PDF documents of version 1.5 and higher can contain cross-reference streams. Read the PDF Reference.

Identify multiple Excel selection ranges passed to VBA.

If I select two ranges of a worksheet from within the worksheet/Excel itself and run a VBA (macro) to perform operations in VBA on the ranges, how do I identify those two selections in the VBA code to work with
them?
In other words, in the work book drag with the mouse to select a range, then Ctrl+drag a second range then call/run the macro/VBA. (For example, right-click drag cells B11 to B14, release, then Ctrl-right-click cell F1 (or F1 to F7). Then run the macro.)
How do I reference those two selected ranges (B11:B14 and F1 or F1:F7from the example) in the VBA code?
I see many example within VBA of selecting multiple ranges, but how do I refer to ones "passed" to the macro? (I'm thinking it would be something like Application.Selection.first and Application.Selection.second, etc but VB doesn't show anything
to choose past Application.Selection .)
Is it even possible to identify that two selections exist or is it all one selection, even if they are disjoint ranges?
If it's all one selection (Application.Selection), how might I identify two non-contiguous ranges from within the selection and "split" them into two?
I just found out that in Excel I can select three non-adjacent cells from any row or column, but I can only copy those three cells if they are on the same row or column. I didn't try more cells.
This is all in Excel 2007.

JimC, you get my ANSWERED vote!
As near as I can tell, it does almost exactly what I need. I tested with four non-contiguous cell selections and the loop displays each one in the order selected.
What it doesn't do is give the range of a contiguous area in the order of selection, meaning selecting e20 to a3 (dragging up to the left) gives range a3 to e20. Essentially, a range bigger than one cell is always identified as lowest order cell
to highest order cell.
I can handle that if needed by selecting individual cells through the range (as long as it's not too many cells) in the order I want to deal with them.

Acrobat Distiller Automation Interface Error

As software developer I try to use the Adobe Acrobat Distiller Automation Interface as described in the document "Acrobat Distiller
API Reference", "Windows Automation".
Now I have found the problem, that if the same user is using the automation interface at the same time, the second user fails with the following error: The server threw an exception. (-2147417851).
I have investigated myself into the problem I discovered that the same user is sharing the acrodist.exe process. How can I now start
an own process to allow parallel execution?
With two different users the problem does not occur.
Thanks for your help
Raphael Affolter

That's what I have done. I have created an own Mutext to synchronize access to the Distiller Interface.
But race conditions exists even with a Mutex on a fast machine because if one process is releasing and the other acquiring the Distiller interface at the same time, the second process may fail.
The documentation says: Each user of the automation interface has its own Distiller instance. There is no sharing of a common Distiller.
Therefore I have tested this and it works fine for different users (even if the EULA prohibits this).
To solve the synchronization and race conditions, even for the same user an own instance should be started or the Distiller should serialize the requests itself (to avoid race condition).
Thanks again
Raphael Affolter

Acrobat Distiller has stopped working

I see this has been posted a couple of times but the issue has not been resolved.
I am running FrameMaker 12, Distiller XI, on Windows 7.
I'm trying to File > Save as PDF and I get the error-- Acrobat Distiller has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.
The only option is to click close. This error appear 3 times before it really stops.
I have investigated this issue to a particular font issue. Although, I do not know how to correct it.
In the Distiller, Settings > Edit Adobe PDF settings , I have selected the folder for Fonts, unchecked Embed all fonts, added my font to the Always Embed list, saved my settings and then used those settings to try the same process again, with the same result.
The font that I want to embed is a free font, so there should not be any license issue with it.

This will not be Distiller Server, I suggest the regular Acrobat Creation forum. Nobody comes to this forum because Distiller Server stopped years ago.

Acrobat Distiller 8 Professional

Hello,
We have the following problem. We have a folder with several MS Word documents. When an MS Word document is created in a specific folder we want them to convert automatically into a PDF document.
Acrobat Distiller 8 Professional have the "watched folder" feature but can only read .ps documents. Is there any solution (maybe another Adobe program) to convert our MS word documents automatically into PDF documents?
Kind regards,
Steven De Smet

>When I post in another forum nobody respons.
I looked into your post in the Acrobat Windows forum.
You seem to have accidentally added this to another topic, rather than
creating a new post with an accurate subject that describes your
problem. The subject is VERY important, as people use this to decide
whether to read your message.
Worse, you added to a thread with the title "Acrobat 8: Extracting &
Printing Highlighted Sentences", which really has no connection at
all.
You also perhaps missed the adivice I gave you "be sure to say the
exact version of Distiller you have, the version of Windows, and when
you get this error message." This is important too.
I recommend you make a new post bearing these points in mind. Good
luck,
Aandi Inston

MARS reference in VBA

Hi,
I was looking for a MARS reference in VBA. I know that there is an equivalent reference in JS (AcroJS if i am not wrong). Is there one in VBA?
Thanks,
Shashank

On the Macintosh, there is no OLE interface to Acrobat at all. The
Acrobat SDK describes the different Macintosh interfaces.
Aandi Inston

Excel Get ActiveX References.vi and closing references -- grrr

I'm new to ActiveX stuff, but eager to learn!
The "grrr" in my Subject line is a reference to how I feel about LabVIEW's documentation from time to time. I'm a dinosaur who came from text-based programming, and did a fair amount of C coding, so sometimes with LabVIEW I'm left with this awful feeling in the pit of my stomach like, "Good grief! How much memory must LabVIEW be hogging up in the background when I use this vi?" or "What happens to those variables (wires) in that subVI when it completes but doesn't close? What are their statuses when I come back in the next time?" or "What if I put a lot of elements into that array the first time and then started from element zero the second time and just put in a few? What has happened with the memroy that was allocated when there were a lot of elements?"
Today I'm stewing about this "Excel Get ActiveX References.vi," and what happens to the "ActiveX references" it generates each time I call the subVI in which "Excel Get ActiveX References.vi" lives. I think that at least one of the "ActiveX references" it generates when I call it is of the type Excel._Application. Then there appears to be an Excel._Workbook, and others. You see, I've used "Excel Easy Report.vi" to put some data into an Excel spreadsheet, and I want to tell Excel to do a "Save" on the open spreadsheet. I think ActiveX is the (a) right way to do that, so I'm wading into the ActiveX fray... But this "Excel Get ActiveX References.vi" says in its help file, "Do not close ActiveX references opened with the Excel Get ActiveX References VI. References must remain open until the report is closed. Otherwise the error 3001 will occur." Well, these Excel workbooks that get created by my VI could well stay open until after my LabVIEW VI terminates!
So (finally), here are some of my quesitons:
1) When I go through my subVI once, pointing to one workbook, I'll get one set of references "created" or "opened" or whatever you call it when ActiveX references spring into existance. Now, when I exit the subVI, is it going to automatically try to "close" those ActiveX references? I don't suppose so, since subVI's stay in memory until the calling VI closes.
2) Now, I come back into my subVI a second time. New workbook gets created, so I get new references. Ok, fine. Uh oh! What happened to those old references? I suppose that if I didn't somehow save them off, I've probably lost the ability to get them back (maybe I'm wrong, but I don't need them back), but is LabVIEW going to "close" those old references (from previous times through the subVI) because I can't get to them anymore? Won't that cause the dreaded error 3001? If LabVIEW is not going to "close" them, what in tarnation happens to them (the old C programmer in me creeping back out)?? Now it's some oddball, orphaned reference, floating out there, hogging memory, waiting to make something crash intermittently and be a debugging nightmare?
3) Now, here's the real scary one. I think I might dodge the "error 3001" bullet in questions 1) and 2), but now let's say the user closes my LabVIEW application while Excel is still open. All those workbooks are still open. Presumably, all those ActiveX references I was not supposed to close are still open. I really hope that LabVIEW is decent enough to close/erase/delete/blow-away (whatever the right word is) all those ActiveX references which were opened/created by "Excel Get ActiveX References.vi" when my program terminates. But, oh no! Won't the error 3001 come along then? I suppose I can just dump it in the shutdown error handling.
Well, thanks for reading my novel. I don't know what can be done with LabVIEW documentation to make it more satisfying to folks like me, but perhaps someone can weigh in on all my ActiveX questions here.
Thank you in advance,
Steve Brady
Solved!
Go to Solution.

You need to close EVERY ActiveX reference you open. If you don't you'll end up with some Excel processes running even after LabVIEW exits. You can see them in Task Manager.
I, personally, don't like the LabVIEW Report Generation Tool Kit for working with Excel. I don't think it's flexible enough. I have a growing library of VIs that I've written that open, manipulate, and close Excel. Some references I pass from VI to VI and some I close right after I use them. It all depends on what I'm doing. If I want to enter read or write data from/to a certain range I'll get the range reference, read or write the data, then close it right away because I have no use for it any more. On the other hand, when I open Excel or a Workbook I keep the reference until I'm done, which could be later in the program.
1) When I go through my subVI once, pointing to one workbook, I'll get one set of references "created" or "opened" or whatever you call it when ActiveX references spring into existence. Now, when I exit the subVI, is it going to automatically try to "close" those ActiveX references? I don't suppose so, since subVI's stay in memory until the calling VI closes.
2) Now, I come back into my subVI a second time. New workbook gets created, so I get new references. Ok, fine. Uh oh! What happened to those old references? I suppose that if I didn't somehow save them off, I've probably lost the ability to get them back (maybe I'm wrong, but I don't need them back), but is LabVIEW going to "close" those old references (from previous times through the subVI) because I can't get to them anymore? Won't that cause the dreaded error 3001? If LabVIEW is not going to "close" them, what in tarnation happens to them (the old C programmer in me creeping back out)?? Now it's some oddball, orphaned reference, floating out there, hogging memory, waiting to make something crash intermittently and be a debugging nightmare?
3) Now, here's the real scary one. I think I might dodge the "error 3001" bullet in questions 1) and 2), but now let's say the user closes my LabVIEW application while Excel is still open. All those workbooks are still open. Presumably, all those ActiveX references I was not supposed to close are still open. I really hope that LabVIEW is decent enough to close/erase/delete/blow-away (whatever the right word is) all those ActiveX references which were opened/created by "Excel Get ActiveX References.vi" when my program terminates. But, oh no! Won't the error 3001 come along then? I suppose I can just dump it in the shutdown error handling.
1) No, LabVIEW will NOT close those references. You need to make sure that happens.
2) You can save the references in a functional global or use a class but if you're not going to save them close them as soon as you're done with them.
3) Your user should not be able to close your LabVIEW application without it going through the shutdown routine you've created for your program. The ABORT button should never be exposed to the user and you should capture and discard the panel close event so your program ALWAYS shuts down is an orderly fashion. If you don't you will have fragments of Excel hanging around in your operating system and will have to kill those processes using Task Manager. That should only be a problem during development, not once deployed.
I used to program in C and Assembly many moons ago. You should have seen my first LabVIEW code. I go back and look at it just so I can see how far I've come in the last 12 years. I feel your pain.
Kelly Bersch
Certified LabVIEW Developer
Kudos are always welcome

Need a driver for Acrobat Distiller 5.0.0.0 that will work on Win 7 Pro SP1 64-bit. How can I find it?

Need a driver for Acrobat Distiller 5.0.0.0 that will work on Win 7 Pro SP1 64-bit. Where can I find it, and what file is it? (Yes, it's an old Distiller that came with Acrobat 5. So shoot me. But I do need the driver.)
Win 7 prompted me for an *.inf file. Any idea?
If I find the original Acrobat 5 CD, which .inf would it be?
(Hey, since I'm asking, also a driver that will work on Win 8.1 Pro 64-bit.)
Thanks.

There is no .inf file on the Acrobat 5 CD that you can use to create a “driver.” If Distiller 5 even installs and runs on Windows 7 x64, the plumbing that came with Acrobat 5 to automatically feed PostScript files created by the PostScript driver to Distiller simply won't work with modern versions of Windows or any 64-bit version of Windows.
FWIW, Acrobat 5 is five full versions back from the current version. And no, we won't shoot you; you are effectively doing that to yourself! Your time must be worth something?!?!
- Dov

How do I add the Acrobat Distiller Printer to my list of printers.

I have Adobe Acrobat 5.0 full version. I would like to know how to convert MS Works files to PDF files.
I keep getting the following message when I try to open a file as a PDF file.
When I open the MIcrsoft Works program and try to print ot the Acrobat Distiller it's not listed as you can see in the image below.
How can I had the Acrobat Distiller to my list of printers.
Please email with an answer Thanks.
[email protected]

Well those listed files you had were of no help. I did some more searching in an system I had and found the downloaded file Acro5.0.5.exe.
I searched for instances of the word Adobe and deleted them including folders. Also cleaned the registry as well then reinstalled the software from the afore mentioned file. Then re-registered the program. Now everthing is working fine, The Acrobat Distiller Printer is now shown in Printers and Faxes Control Panel.
I did some file conversions to PDF and the distiller is now listed as a printer source in the Print Menu of the file I am converting.
Thank for your help.

Acrobat Distiller.app can't be selected when printing to Adobe PDF 9.0

When trying to print a word 2004 doc to Adobe PDF 9.0 ( using the Adobe PDF 9.0 option from the Printer drop-down list within the print dialog box - I have CS4 Design Premium installed including Acrobat Pro 9) I'm asked to locate my copy of Acrobat Distiller in a dialog box. I point it to the correct location. However Acrobat Distiller.app within folder Applications>Acrobat Pro 9 is greyed out and can't be selected. How do I get round this?

Hello lisagig and welcome to Apple Discussions.
I would be inclined to run a repair disk permissions first and if that doesn't help then I would reset your printing system. Note that this will remove all of your current printer queues so if you have a number of network printers in the list it would be handy to make a note of their network queue, which you will see via the Print & Fax > Options & Supplies > General pane shown as URL.
To add the PDF printer queue back, you will need to make the Advanced icon appear in the Add Printer pane. To do this, open Print & Fax and click to Add a printer. Control Click on the current toolbar (next to More Printers will be fine) and select Customize Toolbar. Drag the Advanced icon to the toolbar. Now click the Advanced icon. After a few seconds this pane will become active so you can select the Adobe PDF 8.0 (pdf) in the Type column. Every other column will autofill so leave them as they are except for the Print Using menu, where you will have to open, click 'Select a driver to use' and then type Adobe in the search window. This should show the 'Adobe PDF 3016.102'. Select this and click Add to complete. Now try printing with this new Adobe printer to see if the error has stopped.
Pahu

Acrobat will not let me create a pdf. It says "Acrobate distiller has encountered a problem and needs to close."

I'm using a PC to convert pagemaker files to PDF to send to the newspaper printer exactly as I have done for years. Suddenly Acrobat distiller will not let me create the pdf. Can anyone help me?@@

I did think about that and if I have to I will do that, however there are about 50 songs. I have closed and reopened iTunes several times and I am sure that I have the latest version. It fails right away but I can click on the cloud download icon and download the song that it failed on ... therefore it is not that song "or any one song" causing the issue. Any ideas?

Acrobat Distiller, Excel, Adding a reference in VBA

Similar Messages

Maybe you are looking for