Cells.Find Returns Error When No Match Found

Article translations Article translations
Article ID: 108892 - View products that this article applies to.
This article was previously published under Q108892
Expand all | Collapse all


When you run a recorded Visual Basic for Applications macro, the Cells.Find, Columns.Find, Selection.Find, and Range.Find functions will produce the following macro error if no data is found:
Runtime error '91':
Object variable not Set
This macro error occurs because the Visual Basic Find method returns a NULL value which makes activating a cell impossible.


Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements. The following Visual Basic example will attempt to find the text string "mystring" and produces an alert message which will not cause the macro to halt.
Sub Find_Macro()
    mystring = "mystring"
    Set RangeObj = Cells.Find(What:=mystring, After:=ActiveCell, _
    LookIn:=xlFormulas, LookAt:=xlPart, SearchOrder:=xlByRows, _
    SearchDirection:=xlNext, MatchCase:=False)
    If RangeObj Is Nothing Then MsgBox "Not Found" Else RangeObj.Select
End Sub


Article ID: 108892 - Last Review: October 10, 2006 - Revision: 2.2
  • Microsoft Excel 2000 Standard Edition
  • Microsoft Excel 97 Standard Edition
kbprogramming KB108892

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com