Word 2004 unexpetedly quits after repaging a word 2000 document

[monsterke]

Microsoft Error Reporting log version: 1.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2005-01-11 08:31:19 +0100
Application Name: Microsoft Word
Application Version: 11.1.0.040910
Module Name: unknown
Module Version: unknown
Module Offset: unknown
Extra app info: Reg=English Loc=0x0409


Thread 0 crashed:

# 1 0x566001a4 in ( + 0x00000000)
# 2 0x566001a4 in ( + 0x00000000)

it is a long document and rather big (close to 2MB) with tables and
icons and illustrations in it...
could it be that this is one of the remaining compatibility issues
between word 2000 (windows) and word 2004 for Mac ...

any ideas ?

 

[Daiya Mitchell]

It's probably a corrupt doc--the newer versions of Word (2003 and 2004) are
more sensitive to corruption. Not such which machines you have access to,
but advice on fixing it:

The first way to check for a corrupt document is to
copy the entire thing, *excluding* the last paragraph mark, into a new
document. That last paragraph mark holds a lot of information which can get
corrupted, and copying the text into a document with a fresh one keeps your
formatting, but can fix some glitches.

A paragraph mark is a gray ¶. Click on ¶ on the standard toolbar to show
nonprinting characters, including paragraph marks.
Further info:
Win:
http://www.mvps.org/word/FAQs/AppErrors/CorruptDoc.htm
(hit refresh a few times in Safari, or use a different browser)
Mac:
http://word.mvps.org/MacWordNew/DocumentCorruption.htm
(hit reload a few times in Safari, if that doesn't work, try Explorer)

Tables can also specifically corrupt, for which the fix is Table | Convert
Table to Text, then convert it right back to a table.

DM

 

[matt neuburg]

t is a long document and rather big (close to 2MB) with tables and
icons and illustrations in it...

This sounds like the problem where Word 2004 will crash if it tries
rebuild the table of contents for a document, but Word X rebuilds the
same table of contents just fine. I believe that Microsoft know about
this bug and are working on it. If you watch the repagination dialog you
may be able to see what page is reached at the point where the crash
happens, and you may then be able to find the offending object (almost
certainly a table, icon, or illustration) and remove it. m.