Publisher 2000 cannot open my .php files from an earlier version.

E

elleny

We have some older Publisher files that we were able to print before we went
to Office 2000. The file format is .php. We cannot figure out how we can open
these files. We just suddenly, in one of Microsoft's upgrades, lost the
ability to use these files. Does anyone know how to get these files open in
order to save them as .pub files?
 
E

Ed Bennett

elleny said:
We have some older Publisher files that we were able to print before
we went to Office 2000. The file format is .php. We cannot figure out
how we can open these files. We just suddenly, in one of Microsoft's
upgrades, lost the ability to use these files. Does anyone know how
to get these files open in order to save them as .pub files?

..php files were never created by Microsoft Publisher.
They were probably created by PictureIt Publishing or Home Publishing.
Neither of these is the same as Microsoft Publisher, and neither is
compatible with Microsoft Publisher.
 
J

John Inzer

elleny said:
We have some older Publisher files that we were able to
print before we went to Office 2000. The file format is
.php. We cannot figure out how we can open these files.
We just suddenly, in one of Microsoft's upgrades, lost
the ability to use these files. Does anyone know how to
get these files open in order to save them as .pub files?
=================================
You should be able to open / edit your .php files
with Microsoft Home Publishing or any version
of MS Picture It! / MS Digital Image.

The .php files cannot be converted to Publisher
(.pub) files with the exception of a simple copy/
paste which will only create an image of the
file...not an editable layered project.
 
E

Ed Bennett

Another idiot blaming MS for their own stupidity. ....
How is that Microsoft's fault?

Microsoft must share at least part of the blame, for the sheer stupidity of
naming so many products with similar names.
 
D

drc023

I totally agree with Ed. To be fair Microsoft isn't the only major supplier
to have confusing naming conventions and/or vague instructions. Back in the
good old days when I was in mainframe software support for IBM one of my
biggest complaints was with manuals which had confusing or difficult to find
information. I always considered it a product defect when the resolution to
a problem was in the documentation, but because the manual was so difficult
to decipher multiple customers were encountering the same problems.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top