Results 1 to 5 of 5
  1. #1
    New Lounger
    Join Date
    Jan 2003
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Corrupted Table (Word2000) (9.0.4402 SR-1)

    A couple of times now when I open a Word document I get the (un)helpful message: "A table in this document has become corrupted. To recover...". Fine, but WHICH table! Anyone know an easy way to find out which? The usual "Word formatting issue" work-around of saving in RTF format and reloading clears the error, but I'd still like to know which (of the many) tables is causing the problem. I don't really want to go through an extensive repetive cycle of "delete table/save/close/open" to locate it. Any suggestions?

  2. #2
    5 Star Lounger
    Join Date
    Dec 2000
    Location
    Calgary, Alberta, Canada
    Posts
    818
    Thanks
    6
    Thanked 1 Time in 1 Post

    Re: Corrupted Table (Word2000) (9.0.4402 SR-1)

    Question? Are you using nested Tables? Apparently there are some problems with them when formatted text is copied into them under certain circumstances. If you are not using nested tables, then obviously this is not the problem.

    I would look for things such as objects embedded in table cells. You might also want to do a search of the Microsoft Knowledge Base using "tables+corruption" as your criteria. The other suggestion, knowing Microsoft's penchant for crazy things, is it really a Table that is corrupt ( I had to ask) <img src=/S/shrug.gif border=0 alt=shrug width=39 height=15>

    The other question I have is - how long is this document. On a recent project, we ran into a few problems with some very long documents (still do not know why) that were corrected by your "convert to RTF and reconvert" trick. HTH

    Ron M <img src=/S/smile.gif border=0 alt=smile width=15 height=15> <img src=/S/smile.gif border=0 alt=smile width=15 height=15> <img src=/S/smile.gif border=0 alt=smile width=15 height=15>

  3. #3
    Super Moderator
    Join Date
    Dec 2000
    Location
    New York, NY
    Posts
    2,970
    Thanks
    3
    Thanked 29 Times in 27 Posts

    Re: Corrupted Table (Word2000) (9.0.4402 SR-1)

    This is a particularly annoying one, isn't it? Unfortunately there doesn seem to be any quick way to get to the offending table either, however a perhaps only slightly faster method would be to copy the file into two copies; in copy one keep the first half of the document, in copy two keep the second half.

    See which half of the document then gives the error. Copy that document into two copies and repeat the above halving cycle until you get down to the offending table.

    Come to think of it, that doesn't sound like much fun either!

  4. #4
    3 Star Lounger
    Join Date
    Aug 2002
    Location
    Phoenix, Arizona, USA
    Posts
    205
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Corrupted Table (Word2000) (9.0.4402 SR-1)

    I had this occur with two different users. In their cases, they had deleted a table. Many users do not have the paragraph marks turned on so when they delete, they don't know what they have not included in their delete. I use Cross-Eyes so I was able to determine what happened. To correct the problem, I copied all of the text up to where the table had been to a new document. I then went to just below where the table code showed and copied that portion over to the new document.

  5. #5
    New Lounger
    Join Date
    Jan 2003
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Corrupted Table (Word2000) (9.0.4402 SR-1)

    My thanks to all who have made suggestions. Having a little time to spare I went through the document and deleted ALL the tables. This didn't cure the problem. I then went through deleting chunks of pages at time with no change to the error message every time I did a save/close/reopen. When I deleted the last page of text an empty table appeared out of nowhere! Doing a save/close/reopen at this point hung Word on the "open". This particular document has no complex constructions in it, but obviously Word somehow managed to corrupt something at some point. I still find it incredible that a sophisticated(?) product such as this has an error message which can be paraphrased as: "I've found something wrong in your document, here's how to fix it, but I'm not going to tell you where it is - that's your problem".

    David

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •