Problem saving PDF within VBA

[Wi11y13]

I am trying to save a slide in pdf format using Powerpoint 2007. I am finding
that it works on some machines but not others. The specifics are Powerpoint
2007, Adobe Reader 9.2. Here is the code:

Set oTempPres = Presentations.Open("c:\Cert.pptx", WithWindow:=False)
With oTempPres
For x = .Slides.Count To 1 Step -1
If .Slides(x).SlideIndex <> currentSlide Then
.Slides(x).Delete
End If
Next
.SaveCopyAs "c:\Cert.pptx"
.SaveAs FileName:="c:\Cert.pdf", fileformat:=ppSaveAsPDF
...........

I know some of you have assisted me within this forum before and have been a
great help. Anyone have any idea why this might work sometimes and not
others. It always works on my machine - whether I am executing the module
from the web (I know it is actually doing the executing on my machine) or
locally. This really has me frustrated now :-(

Thanks so much for the help..

 

[Shyam Pillai]

Hi,
Do you have the Save As PDF add-in for Office 2007 installed? You can only
run the ppSaveAsPDF enum if it is installed else it will give an automation
error.

Regards,
Shyam Pillai

Image Importer Wizard: http://skp.mvps.org/iiw.htm

 

[Wi11y13]

If we execute this module from a server, does this add-on need to be
installed on every client that runs it? I know that the PP instructions are
actually being executed from the client and not the server is why I ask. Is
there another way to actually save the slide in pdf format? I am worried that
not everyone would have this add-on on their machine and it could be executed
both from inside the University and from a private machine at home. Not sure
I can require the add-on for every machine which is why maybe another
solution might work if there is one.

Thanks again for the help.

 

[Wi11y13]

Thanks Steve. As always - jolly on the spot

We are accessing the module through a central server but the actions are
actually taking place on the client (each client needed a registry change in
order to download and execute the .ppsm file correctly) so now each client
also needs this add-on.

Again, kudos to you and this discussion group......