Shasur, thanks much!
While it was incredibly helpful, I do hope maybe you can provide some additional support.
I think this may be a problem with Word itself, so I don't know if there's a workaround. These documents have tables in them as well. Neither your procedure nor mine will move through a table if a row or column has been deleted. Trying it manually, it gets to a deleted a row or column, and sees that as the end of document, and asks if you'd like to return to the top. Fortunately, these are closer to the end than the beginning, but still, it's a hassle to highlight manually. Any thoughts on this?
*Edit.... It went through my first table just fine, which had deleted columns. The second table, it would do anything, not even highlight changes prior to a deleted column or row. The only things between the stopping point and the table are deleted text (which it has ignored on all other pages) and format changes (same ones ignored on previous changes). It did state an issue with:
Debug.Print ActiveDocument.Revisions(i).Type
Also, the document is 51 pages with changes tracked. Your code moved through 49 pages........in ten minutes. Do you think there may be a way to speed it up at all? If not, it's still much, much faster than doing it by hand.
Thanks again!
|