.Findnext: wrap, or == Nothing ??

[Gates Is Antichrist]

Which is it? XL2002 Help is contradictory. They test a .Findnext loop against Nothing; yet they say (as we all know) that it DOES wrap around.

Is what really happens that you get "one Nothing per wraparound?"

Note: I have been able to force a Nothing, and you can too, using what I perceive as an XL2002 bug:
merge b2 to c3. Type FOO in B2.
put cursor on a1
Ctrl-F
Type FOO
Hit enter twice.

Merged cells and finds are certainly a nightmare. Anyway, is there any other way that you can get Nothing on findnext?

(Well, I can think of another - moving off the active sheet, or selecting an unmatching range, and going shift-F4! Is their test against nothing simply to address things like that?)

 

[parry]

I presume you are following the example in VBA Help under the topic Find Method. The variable c will be nothing if the value of c is changed as part of the loop code. However testing against the address will exit the loop so testing whether c is nothing in the loop while line is superfluous.

In fact if c is nothing you will get a runtime error 91 object variable not set.

Sub test()
With Worksheets(1).UsedRange
    Set c = .Find(5, LookIn:=xlValues)
    If Not c Is Nothing Then
        firstAddress = c.Address
        Do
            c.Value = 43
            Set c = .FindNext(c)
            If c Is Nothing Then MsgBox "c is nothing"
        'The following line will produce an error
        Loop While Not c Is Nothing And c.Address <> firstAddress
    End If
End With
End Sub

 

[Gates Is Antichrist]

Ah, modifying c between the .Find and .Findnext - talk about tampering with mother nature!

Okay, I guess I get it - the Nothing test in the help example was superfluous only for their example. And it IS meaningful if the active region changes, the search range is modified, or if there's a merged cell.

Thanks