> Am I the only one who finds that find doesn't.
>
> e.g. if I search for .Filter it only finds some of the matches.
> If I use Use Pattern Matching and I do *.Filter it finds the others.
> In all cases something proceeds the .Filter  e.g. tType.Filter
>
> And sometimes, like just a few minutes ago, I was searching for sContains
> and it did not find but only a few of the total.
>
> I do a search and replace the attempt a compile only to be told that
> sContains is not defined (because I changed the definition but did not find
> all the usage).
>
> Yes, I had Current Project selected and Find Whole Word as necessary.
>
> I know, reinstall Windoz and the IDE.
> Or ... ?

"Karl E. Peterson" wrote:

> Bee wrote:
> > Am I the only one who finds that find doesn't.
> >
> > e.g. if I search for .Filter it only finds some of the matches.
> > If I use Use Pattern Matching and I do *.Filter it finds the others.
> > In all cases something proceeds the .Filter  e.g. tType.Filter
> >
> > And sometimes, like just a few minutes ago, I was searching for sContains
> > and it did not find but only a few of the total.
> >
> > I do a search and replace the attempt a compile only to be told that
> > sContains is not defined (because I changed the definition but did not find
> > all the usage).
> >
> > Yes, I had Current Project selected and Find Whole Word as necessary.
> >
> > I know, reinstall Windoz and the IDE.
> > Or ... ?
>
> The only time I've seen Find "fail" is when I don't have "Current Project" selected
> (and it's just searching the current module) or if I have any of the checkboxes
> checked (those tend to confuse me more than VB, though, it seems).  I can't imagine
> a reinstall would help.
> --
> ..NET: It's About Trust!
>  http://vfred.mvps.org
>
>
>

"Nobody" wrote:

> Is "Direction" set to "All"?
>
>
>

"Bee" <B**@discussions.microsoft.com> wrote in message
news:E813DBB6-0BB7-493A-8578-8A2AF91D8E9B@microsoft.com...
> Am I the only one who finds that find doesn't.
>
> e.g. if I search for .Filter it only finds some of the matches.
> If I use Use Pattern Matching and I do *.Filter it finds the others.
> In all cases something proceeds the .Filter  e.g. tType.Filter
>
> And sometimes, like just a few minutes ago, I was searching for sContains
> and it did not find but only a few of the total.
>
> I do a search and replace the attempt a compile only to be told that
> sContains is not defined (because I changed the definition but did not
> find
> all the usage).
>
> Yes, I had Current Project selected and Find Whole Word as necessary.
>
> I know, reinstall Windoz and the IDE.
> Or ... ?

"MikeD" wrote:

>
> "Bee" <B**@discussions.microsoft.com> wrote in message
> news:E813DBB6-0BB7-493A-8578-8A2AF91D8E9B@microsoft.com...
> > Am I the only one who finds that find doesn't.
> >
> > e.g. if I search for .Filter it only finds some of the matches.
> > If I use Use Pattern Matching and I do *.Filter it finds the others.
> > In all cases something proceeds the .Filter  e.g. tType.Filter
> >
> > And sometimes, like just a few minutes ago, I was searching for sContains
> > and it did not find but only a few of the total.
> >
> > I do a search and replace the attempt a compile only to be told that
> > sContains is not defined (because I changed the definition but did not
> > find
> > all the usage).
> >
> > Yes, I had Current Project selected and Find Whole Word as necessary.
> >
> > I know, reinstall Windoz and the IDE.
> > Or ... ?
>
> FWIW, I've never found that Find wouldn't find what it's supposed to except
> when it's been my fault (the options not set properly). I hope you were
> being facetious about reinstalling Windows and VB (and don't call it
> Windoz...that's just being immature IMO).
>
> It's most likely the options you have set.  The "Find Whole Word Only"
> option I've noticed can throw a wrench into things. If the text you're
> searching for is actually ".Filter", the dot *may* be causing the problem if
> Find Whole Word Only is checked.  VB's Find is smart enough to know that if
> you search for "Filter" and have "Find Whole Word Only" and "Match Case"
> checked, it'll find "Filter" in "tType.Filter". OTOH, if you search for
> ".Filter" (with those same options checked) it WON'T find it. Unchecking
> "Find Whole Word Only" will find ".Filter". Basically, if you do a "Find
> Whole Word Only" search, don't include punctuation in what you're trying to
> find because that screws up the entire "whole word only" concept.  You gotta
> remember that VB's Find is designed for the language's syntax. It doesn't
> work quite the same way as a Find does in MS Word or a text editor (nor
> should it).
>
> Also, JUST to be sure....this isn't a project group is it? VB's Find won't
> search all projects in a group...only the current project (assuming that
> option is marked).
>
> If you find VB's Find lacking, you might want to try MZ-Tools.  It's Find
> can search all projects in a project group and has other options (such as to
> exclude comments from being searched).
>
> Bottom line...I seriously doubt it's VB and it's certainly not Windows.
> It's just the text you're searching for and the options you've marked.
>
> --
> Mike
>
>

> DNA
>
> Every time this happens I check the options for find and none are set
> incorrectly.
>
> Next time I see if the MZTools does the same thing and report back.
>
> Do you like WinDoes better?
>
> "MikeD" wrote:
>
>> "Bee" <B**@discussions.microsoft.com> wrote in message
>> news:E813DBB6-0BB7-493A-8578-8A2AF91D8E9B@microsoft.com...
>>> Am I the only one who finds that find doesn't.
>>>
>>> e.g. if I search for .Filter it only finds some of the matches.
>>> If I use Use Pattern Matching and I do *.Filter it finds the others.
>>> In all cases something proceeds the .Filter  e.g. tType.Filter
>>>
>>> And sometimes, like just a few minutes ago, I was searching for sContains
>>> and it did not find but only a few of the total.
>>>
>>> I do a search and replace the attempt a compile only to be told that
>>> sContains is not defined (because I changed the definition but did not
>>> find
>>> all the usage).
>>>
>>> Yes, I had Current Project selected and Find Whole Word as necessary.
>>>
>>> I know, reinstall Windoz and the IDE.
>>> Or ... ?
>> FWIW, I've never found that Find wouldn't find what it's supposed to except
>> when it's been my fault (the options not set properly). I hope you were
>> being facetious about reinstalling Windows and VB (and don't call it
>> Windoz...that's just being immature IMO).
>>
>> It's most likely the options you have set.  The "Find Whole Word Only"
>> option I've noticed can throw a wrench into things. If the text you're
>> searching for is actually ".Filter", the dot *may* be causing the problem if
>> Find Whole Word Only is checked.  VB's Find is smart enough to know that if
>> you search for "Filter" and have "Find Whole Word Only" and "Match Case"
>> checked, it'll find "Filter" in "tType.Filter". OTOH, if you search for
>> ".Filter" (with those same options checked) it WON'T find it. Unchecking
>> "Find Whole Word Only" will find ".Filter". Basically, if you do a "Find
>> Whole Word Only" search, don't include punctuation in what you're trying to
>> find because that screws up the entire "whole word only" concept.  You gotta
>> remember that VB's Find is designed for the language's syntax. It doesn't
>> work quite the same way as a Find does in MS Word or a text editor (nor
>> should it).
>>
>> Also, JUST to be sure....this isn't a project group is it? VB's Find won't
>> search all projects in a group...only the current project (assuming that
>> option is marked).
>>
>> If you find VB's Find lacking, you might want to try MZ-Tools.  It's Find
>> can search all projects in a project group and has other options (such as to
>> exclude comments from being searched).
>>
>> Bottom line...I seriously doubt it's VB and it's certainly not Windows.
>> It's just the text you're searching for and the options you've marked.
>>
>> --
>> Mike
>>
>>