Auric__ wrote :
GS wrote:

Auric__ laid this down on his screen :
GS wrote:

You might want to get into the habit of specifying a value since InStr
can result unexpected behavior if you assume it's return value is
equal to vbFalse...

If InStr(rngC, "Milka") 0 Then

I generally just go by the old standby, "0 is false, anything else is
true." It's been working for ~29 years now...

That's safe in VB but VBA will bite you with that assumption!

Clarify please? I have several places where I use InStr(x, y) as an implied
boolean value, and have never noticed a problem.

See Karl's explanation under the topic "Boolean games" in
microsoft.public.vb.general for clarification of my point. Clearly it
doesn't apply to your usage here, but Karl notes the exceptions where
it doesn't work in VB/VBA as expected.

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion