(Continued from previous message)
        created in step 5 above.
11)     Choose File new to create a new document. Insert the RTF 
        file into this document, but insert it as a plain ASCII 
        text file, not as an RTF file. You will see all the RTF 
        edit codes in the document. Ugly, eh? Save this file with 
        a transient name (Eraseme.txt is good!) 
12)     Locate the starting point of the corrupt text, delete the 
        RTF codes, and paste the rescued text, without its 
        formatting, at the end of the Code1 file from step 8 
        above.
        
13)     Locate the ending point of the corrupt text, delete the 
        RTF codes, and paste the rescued text, without its 
        formatting, at the start of the Code2 file from step 9 
        above.
14)     Glue the Code1 and Code2 to form a new document. 
15)     If you had only one point of corruption (e.g. 13/21 and 
        13/21) you are done. If you had more than one point of 
        corruption (e.g 6/22 and 8/22 as in my example), then the 
        new document formed from Code1 and Code 2 still has 
        corruption. Start again at step 2 above and weed out the 
        next two corruption points.
                                BOOKMARKS
                                =========
This time around I was in an 800 kilobyte MSWord 6.0c document 
        which had been built as a series of bookmarked text items 
        (some 700 of them!). I was able to navigate well by 
        judicious use of the Edit Bookmark command, first 
        selecting (click once) the bookmark which appeared at the 
        top of the screen in step 2 above, and then switching to 
        "display by location" in the Edit Bookmark Dialogue box 
        to determine the bookmarks geographically preceding the 
        leading point of corruption. A similar technique let me 
        examine bookmarks following the trailing point of 
        corruption. 
Use any auxiliary structure available to you in order to move as 
        close as possible to the point of corruption without 
        freezing the system.
CREDITS
=======
... are due to the staff of Microsoft's help desk in Markham 
        Ontario for holding my hand as I formulated these steps. 
        You done real good, guys!
And while we're at it, thanks to every BBS Sysop who made the 
        transmission of this message possible.
christopher.greaves at pro-mail.com and at ablelink.org 
                    www.interlog.com/~cgreaves
 * 1st 2.00b #6263 * People and Computers
--- PCBoard (R) v15.3 (OS/2) 5
---------------