Thank you Dave but i am not aware of a PDFmaker addin being installed on this
machine. I have adobe 5.0 and reader 8.0 installed however I did not have
this issue with office 2003
> If you're not using the pdfmaker.* addin, how about just closing excel and using
> windows|search to find that file and move it to a different location (or delete
[quoted text clipped - 8 lines]
> > before you can get into excel.
> > Hope I got this in the correct discution group.
Dave Peterson - 23 Feb 2007 21:19 GMT
I'd still look for PDFMaker.OLDxla.
Even if you don't think you have it, excel does.
(Although, I've never seen PDFMaker.OLDxla. But problems with PDFMaker.xla are
the subject of many posts around here.)
> Thank you Dave but i am not aware of a PDFmaker addin being installed on this
> machine. I have adobe 5.0 and reader 8.0 installed however I did not have
[quoted text clipped - 16 lines]
> >
> > Dave Peterson

Signature
Dave Peterson
marshallemail@comcast.net - 24 Feb 2007 01:21 GMT
Jim,
I get the same message when I try to open a file with a custom
extension that has been associated with Excel. I would like to find a
way to bypass the message but haven't had success yet. If I figure
anything out, I'll post back.
Tom
> Thank you Dave but i am not aware of a PDFmaker addin being installed on this
> machine. I have adobe 5.0 and reader 8.0 installed however I did not have
[quoted text clipped - 16 lines]
>
> > Dave Peterson