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

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?

elleny was very recently heard to
utter:
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.

--
Ed Bennett - MVP Microsoft Publisher

elleny wrote:
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.

--

John Inzer

On Fri, 21 Oct 2005 08:40:02 +0100, elleny wrote
(in article ):

We have some older Publisher files


Er, no, you don't.


that we were able to print before we went to Office 2000.

And if you still had the correct application installed you'd still be able to
print them.

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.

Another idiot blaming MS for their own stupidity. Nothing whatsoever to do
with "MS's upgrades" and everything to do with you uninstalling the
application. How is that Microsoft's fault?


Does anyone know how to get these files open in
order to save them as .pub files?


You cannot save them as .pub files as they did not, do not and will never
have anything to do with MS Publisher. You reinstall the application *you*
used to create them.

was very
recently heard to utter:
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.

--
Ed Bennett - MVP Microsoft Publisher

On Fri, 21 Oct 2005 16:02:33 +0100, Ed Bennett wrote
(in article ):

was very
recently heard to utter:
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.



I disagree. Anyone with half a brain can tell the difference. Trouble is most
we get in here aren't far enough up the evolutionary tree to have developed
the necessary faculties.

I've made the same comment MANY times.

--

JoAnn Paules
MVP Microsoft [Publisher]



"Ed Bennett" wrote in message
...
was very
recently heard to utter:
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.

--
Ed Bennett - MVP Microsoft Publisher

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.
--
Ron

"Ed Bennett" wrote in message
...
was very
recently heard to utter:
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.

--
Ed Bennett - MVP Microsoft Publisher