Re: A .doc file created using Word2000 can not be opened by Word2003

From: Beth Melton (bmelton_at_NoSpam4Memvps.org)
Date: 10/27/04 

Date: Wed, 27 Oct 2004 16:45:42 -0500

There have been a few reports of various issues, primarily if the
document contains, or ever contained, old Clipart.

What does the document contain?

If you are encountering issues then you don't need to save it as RTF.
The Word 2003 user should be able to open the document using the "Open
and Repair" command found in the Open dialog box under the Open drop
down menu. Note that the need to use the Repair command doesn't
necessarily mean the document is corrupt, it means there is something
in the binary that the newer version of Word is unable to interpret. 

-- 
Please post all follow-up questions to the newsgroup. Requests for 
assistance by email can not be acknowledged.
~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP
Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/
"microsoft" <hmccoy@ableinnovations.com> wrote in message 
news:O8nqryFvEHA.3416@TK2MSFTNGP09.phx.gbl...
>I have created a .doc file using MS Word 2000.  When our client tried 
>to
> open the file in Word 2003, she received a message says "It is 
> corrupt".
> When I saved the file in .rtf format, she was able to open the file.
>
>
>
> One thing I have noticed is when I modified the original .doc file a 
> little
> and saved it with Word 2000, the file size became from the original 
> 200K to
> almost 2MB.
>
> The modification I made was very small.
>
> Can anybody tell me if this is a bug of Word 2000?
>
>
>
> Also is this bug the cause of not being able to open the file in 
> Word 2003?
>
>
>
> Next thing I tried was cut and pasted the entire document to a new 
> document
> and re-saved it.
>
> Then the file size became smaller as the original, but still the 
> client
> couldn¡¯t open the file in Word 2003.
> I understand that there is a way to open a corrupt file in Word2003 
> from
> Open dialog box, but I'd like to avoid this somehow embarrassing 
> situation
> when we send the file to the client.
> Please advice...
> Hilo

Relevant Pages

  • Re: Delphi 8 common quality
    ... > Come on - you cannot seriously believe that is providing the customer ... If I have a client reporting issues as side comments or not directly related ... solving the bug the issues rather than how the bug gets recorded. ... Borland or TeamB to pick up on the bug and carry it along. ...
    (borland.public.delphi.non-technical)
  • NOT GOOD: Outlook Express 6 + Internet Explorer 6
    ... Internet Explorer 'bug' presently in the wild [original ... the Microsoft Internet Explorer browser. ... Express email client from the same merchant might be necessary: ... What we then do is construct our original functional demo to: ...
    (NT-Bugtraq)
  • [Full-Disclosure] NOT GOOD: Outlook Express 6 + Internet Explorer 6
    ... Internet Explorer 'bug' presently in the wild [original ... the Microsoft Internet Explorer browser. ... Express email client from the same merchant might be necessary: ... What we then do is construct our original functional demo to: ...
    (Full-Disclosure)
  • NOT GOOD: Outlook Express 6 + Internet Explorer 6
    ... Internet Explorer 'bug' presently in the wild [original ... the Microsoft Internet Explorer browser. ... Express email client from the same merchant might be necessary: ... What we then do is construct our original functional demo to: ...
    (Bugtraq)
  • [patch 30/47] tcp: fix skb vs fack_count out-of-sync condition
    ... -stable review patch. ... This bug is able to corrupt fackets_out in very rare cases. ... need to scan that entry twice or didn't dare to make it go ...
    (Linux-Kernel)