Difference between Intersect and Not Intersect is Nothing

**batman** · 11-12-2009, 11:35 PM

My app uses Worksheet_Change(ByVal, Target as Excel.Range)

To narrow the scope of the event I then use either:

Please Login or Register  to view this content.

The large majority of code samples that I've seen for the Change Event all use the first form. Yet intuitively I would expect the 2nd form to be operationally identical since NOT and IS NOTHING appear to cancel each other. And because it eliminates NOT and IS NOTHING, the 2nd form ought to be more efficient. In fact, in my application the 2nd form seems to do the same thing and work just as well. Is there some gotcha or subtle distinction between the two forms that I should be aware of?

**Leith Ross** · 11-12-2009, 11:51 PM

Hello Batman,

The comparator statement Is Nothing is used exclusively with objects. Target is a Range object and Intersect returns either a Range object, if true, or Nothing.

**batman** · 11-13-2009, 05:39 PM

Thanks Leith, that helps.

While pondering your response and studying my code, I realized that I don't need the Intersect code line at all. I already know the range (Trading) where the changes take place, and with or without the Intersect statement I can deal explicitly with the consequences of the specific change. Using Worksheet_Change simply tells me when to take that action. So I commented out the If.....Intersect..... line and its mating End If, and everything worked fine - same results as before. I'll mark the thread solved.