Although Grant has signed off until further notice <img src=/S/grin.gif border=0 alt=grin width=15 height=15>, I'm still puzzing over this:
<hr>As a spot of background, the reason I am trying to use this instead of the VBA equivalent is that there is a horrible bug in the "Revisions" object in VBA which prevents it accessing revisions within tables.<hr>- which horrible bug is being referred to, and what does
WordBasic.ToolsReviewRevisions FindNext:=True, Wrap:=0
When I test these, they behave exactly the same.
There is one shortcoming - which is the same with both of these - when it comes to revisions in tables - both of these commands will not select individual revisions in table cells, but rather will select the entire row that a revision is found in.
This is a very annoying limitation, but I think it's related to a built-in limitation in Word's comparison feature (at least through Word 2000 anway; haven't tested on Word 2002 where track changes was supposedly revamped) - if you do a Word Compare Documents on documents that feature revisions in tables, you will get entire rows duplicated, with one marked as an insertion and one marked as a revision, even if there was literally just one character changed in one cell.
This, despite the fact that when using the Track Changes While Editing feature, you can mark individual changes inside cells.
This definitely seems like a bug in the VBA object model, but based on a quick test at least, the WordBasic command has the same limitation.
Hmm, perhaps we'll never get to the bottom of this (unless Grant is checks in on this thread again <img src=/S/eyeout.gif border=0 alt=eyeout width=15 height=15>).