powperpoint automation with missing embedded fonts

[Dana]

I am facing a problem opening a powerpoint file from a VB application. The
file contains some missing embedded fonts. I have office 2003. What I want
to do is to save the file to html format.

I can do that with other files but with this particular file I always get an
error. When I open the file normally from Powerpoint directly in Read-only
mode I can see that the "save" and "save as" menues are all disabled.

Can someone help.

 

[Steve Rindsberg]

I am facing a problem opening a powerpoint file from a VB application. The
file contains some missing embedded fonts. I have office 2003. What I want
to do is to save the file to html format.

I can do that with other files but with this particular file I always get an
error. When I open the file normally from Powerpoint directly in Read-only
mode I can see that the "save" and "save as" menues are all disabled.

Most likely it's in Read Only mode because there's an embedded font that you
don't have on your PC as you've already mentioned, and because the embedded
font permits only a type of embedding that allows the recipient to view the
presentation but not to edit it. As a result, PPT disables all editing and
saving functions.

If you have SP2 or later installed, you should be able to use Format, Replace
Fonts to substitute a different *available* font for the unavailable one. That
should then allow you to open/save as you wish.

 

[Dana]

HI Steve

Yes, I have SP2 and I know that I can do that. However, as I mentioned, I am
using VB to open the presentation automatically, therefore I don't know what
fonts are exactly missing, or probably I don't know how to do so.

Any ideas??

 

[Steve Rindsberg]

HI Steve

Yes, I have SP2 and I know that I can do that. However, as I mentioned, I am
using VB to open the presentation automatically, therefore I don't know what
fonts are exactly missing, or probably I don't know how to do so.

Any ideas??

It's possible to iterate through the .Fonts collection of a presentation.
Each .Font object has properties like .Embeddable and .Embedded you can test
against, but honestly, the last time I tested this, the results weren't
reliable.

You might have to try to change something in the presentation, trap the
resulting error (that I'll ... oops ... assume will occur) and kick it back to
the user to fix. Not pretty, I know.