Cross-reference fields update in Track Changes (Word XP)

Topic

New Reply

Hi everyone,

I support a lot of authors who write clinical study reports (CSRs). In these CSRs they’ll have lots of cross-refs to publications (journal articles, stuff like that). We do these by creating a bookmark around the article’s author’s last name, then do Insert…Reference…Cross-reference and choose Bookmark as the type.

Here’s our problem. When we send these CSRs for review internally and use Track Changes, **some** of the cross-refs will show as changes, and not others. We don’t want ANY of them to show as tracked changes.

Does anyone know 1) why some would show and others wouldn’t? (My theory: because these are people’s names and “Detect language automatically” may be turned on, Word changes the language for some of them and not others) and 2) a way to prevent them from showing as tracked changes?

I tried to post an example but of course I can’t get Word to do it right now.

Reply | Quote

Replies

Hi itsjustb,

It could be to do with pagination changes when the reviewers open the document using a different printer driver to the one used when the document was saved, or to changes made during the review process. This is especially so if page/paragraph number cross-refernces are involved.

Here’s a macro to accept all fields showing up as tracked changes:

Sub AcceptTrackedFields()
Dim oRange As Word.Range      ' All Range objects - includes ranges in the body, headers, footers & shapes
Dim Fld As Field              ' Field Object
With ActiveDocument
    ' Loop through all range objects and accept tracked changes on fields
    For Each oRange In .StoryRanges
        Do
            For Each Fld In oRange.Fields
                Fld.Select
                Selection.Range.Revisions.AcceptAll
            Next
            Set oRange = oRange.NextStoryRange
        Loop Until oRange Is Nothing
    Next
End With
End Sub

You could, if you prefer, include this code in the document as an auto_open macro.

Cheers,
Paul Edstein
[Fmr MS MVP - Word]

Reply | Quote

I hadn’t considered the pagination update being the trigger–the whole company is supposed to be on the same driver, but we’re not.

That code will get me where I need! THANKS.

Reply | Quote