MsgBox is lazy or disobedient

Hi Excel Forum

I thought I at least had a kindergarten type understanding of VBA, but something is tripping me up here and I suspect I shall deserve to be bopped on the head with a saucepan when the solution is explained to me.

The following code searches Column A for a cell that contains a string equaling the one stored in drop_point. (Since I'm not experienced at VBA I'm putting this program together in baby steps and using MsgBox way too often just to make sure, at this point, that I'm working with the cells I think I am.)

dp2_cell has already been declared as an Object; drop_point as a string, and dp_search and sheet1_row_counter as integers.

The cell we're hoping to land on is A2. Indeed, when this code runs, things seem to stop happening when A2 is highlighted. That's the good news. However, since the "wrong" value is in A1, I expected to see a MsgBox pop up saying "Not it!" and thus for me to have to click its OK button before anything else moved forward. Instead what happens is, I see no MsgBoxes. Neither the "Not It" one when cell A1 is being checked, nor the "Found It!" one when A2 has been reached and everything else stops.

What. The heck. Am I missing here.

Please Login or Register  to view this content.

MsgBox can be your friend.
I would suggest using it to indicate your sub has reached this loop
(If neither message is being printed by the IF, perhaps the IF is not being executed.)

Please Login or Register  to view this content.

Should those messages not appear, then your error is elsewhere, perhaps a logical error.

It looks like your error is in variable naming.

The second line of code:

Please Login or Register  to view this content.

The third line of code:

Please Login or Register  to view this content.

There's an extra underscore between "sheet" and "1".

I would highly recommend using

Please Login or Register  to view this content.

in your macros, which would have helped you catch this error by letting you know that

Please Login or Register  to view this content.

was an undeclared variable.

I TOLD you I was going to deserve a saucepan-to-the-head!!

Thanks so much guys. Here I was, thinking, "Wow, I'm doing such a good job of explicitly declaring my variables, I don't even need to use Option Explicit!" (losing-game-show tuba sounds...)

It happens to the best of us haha.

Just remember that even on your BEST day,

Please Login or Register  to view this content.

is still better than you at finding typos