 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWordDirectoryUser Groups Related Topics Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ... |
MS Office Forum / Publisher / General MS Publisher Questions / October 2005Publisher 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? > 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.  SignatureEd Bennett - MVP Microsoft Publisher > 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. SignatureJohn Inzer > 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. > 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. SignatureEd Bennett - MVP Microsoft Publisher >> 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. SignatureJoAnn Paules MVP Microsoft [Publisher] >> 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 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. SignatureRon >> 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. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.