Re: Publisher cannot open file
Ed Bennett
> 5) recovering the text in Word - only produced gibberish
Somewhere in amongst all the gibberish is the text of your publication.
If there's not much, it may be easier to retype from memory than to look
for it.
> any other suggestions?
Try looking through your temp files for pub*.tmp. Copy to your desktop,
rename to a .pub extension, and try opening them. You might get an old
version of your file.
--
Ed Bennett - MVP Microsoft Publisher
http://ed.mvps.org
Mary Sauer
Where did you get the pictures?
--
Mary Sauer MSFT MVP
http://office.microsoft.com/
http://msauer.mvps.org/
news://msnews.microsoft.com
"Ken Dunkley" <KenDu...@discussions.microsoft.com> wrote in message
news:E420F9D2-2E26-4DEF...@microsoft.com...
> Thanks Ed,
>
> 1) the publication is mostly pictures, so the text is the easy bit
>
> 2) tried looking for the *.tmp file, but my efforts at 'cleaning up' and
> error checking the hard drive have erased all temp files
>
> any other ideas?
Ken Dunkley
2003 and it only occurs with one specific file.
So far, I've tried, without any success....
1) opening the file on two other PC's
2) turning off virus scan
3) running "detect & repair"
4) everything in KB198256, including Safe Mode and disabling the pictures
5) recovering the text in Word - only produced gibberish
6) adding a registry key as described in another KB article - which killed IE
7) cleaning the registry
any other suggestions?
Ken Dunkley
If I have a 'corrupt image', and try to re-create exactly the same layout,
surely the same problem will re-occur.
What makes an image 'corrupt'? How can I check images before I insert them
to see if they are 'corrupt'?
Ed Bennett
> If I have a 'corrupt image', and try to re-create exactly the same layout,
> surely the same problem will re-occur.
Not necessarily
> What makes an image 'corrupt'? How can I check images before I insert them
> to see if they are 'corrupt'?
Damage to the internal structure of a publication is the most likely
cause. Images that are outright corrupt will normally just fail to
import at all.
Ways to avoid corruption are:
a) Avoid saving to or loading from network drives and removable media.
Copy to your local hard drive, work, save, then copy back again.
b) Take very regular and frequent backup copies of your publication
c) Avoid recycling last week's newsletter publication file to create
this week's. Create a blank newsletter from scratch, then save it as a
Publisher Template, which can be used as the basis for each new publication.
d) Replace Norton AntiVirus with a half-competent solution. I haven't
heard of any direct link between teh two, but I wouldn't be surprised if
there were one. And besides, it's not easy to et funding to research the
connection between Publisher file corruption and the presence of Norton
AntiVirus.
If you do find an image that won't import (or that consistently corrupts
your publication), then I suggest running it through IrfanView
(www.irfanview.com) to either recompress it in its current format, or
convert it to a new one.
dondiscumaci
EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com
Mary Sauer
How to troubleshoot a damaged publication in Publisher
http://support.microsoft.com/kb/198256/en-us
--
Mary Sauer MSFT MVP
http://office.microsoft.com/
http://msauer.mvps.org/
news://msnews.microsoft.com
"Dondi Scumaci" wrote in message news:2007827115...@msn.com...