Why does Range.Find.Execute yield a range that is outside the original search range

Question

Answer 1

Using VBA, you could use

Dim rngsearch As Range
Dim boolfound As Boolean
Set rngsearch = Selection.Range
boolfound = False
With Selection
    .HomeKey wdStory
    With .Find
        Do While .Execute(FindText:="coordinated", Forward:=True, _
        MatchWildcards:=False, Wrap:=wdFindStop, MatchCase:=True) = True
            If Selection.Range.Start >= rngsearch.Start And Selection.Range.End <= rngsearch.End Then
                boolfound = True
            End If
            Selection.Collapse wdCollapseEnd
        Loop
    End With
End With
        
If boolfound = True Then
    MsgBox "The text that you were searching for exists within the selected range."
Else
    MsgBox "The text that you were searching for does not exist within the selected range."
End If

Answer 2

I believe that the explanation is that executing a Find will redefine the Range for the search. A common workaround is to add a check to verify that the search is still being done in the originally defined Range.

Experienced VBA coders such @Doug Robbins - MVP and @Jay Freedman may offer more detailed suggestions.

Answer 3

I have found a workaround to this ludicrous MS Word behaviour: If searching forward in the range [A,B] and the text is found before A, then iteratively search backward in the range [A,B] for the last occurrence of the text. If searching backward in the range [A,B] and the text is found after B, then iteratively search forward in the range [A,B] for the last occurrence of the text. Looking at the data produced, searching forward (backward) in the range [A,B] finds text before A (after B) when it is closer than any occurrence actually within the search range itself.