Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
Windows Vista File Management Issues or questions in relation to Vista's file management. (microsoft.public.windows.vista.file_management) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
Windows Search 4 - Wildcard in file content
Hi,
firstly, apologies if this post lands in the wrong groups. Have Windows Search 4 in use under XP pro. Works rather nicely - but - although I can use wildcards such as "*" for file names - use of wildcards for words contained in file content does not work for the word begining. So, in a content search, bana* will find banana but *nana will NOT find banana. Am unsure if this is by design or if I am goofing somewhere. Could anyone please advise? |
|
|||
Windows Search 4 - Wildcard in file content
On Tue, 22 Sep 2009 02:02:01 -0700, Ken-T
wrote: Have Windows Search 4 in use under XP pro. Works rather nicely - but - although I can use wildcards such as "*" for file names - use of wildcards for words contained in file content does not work for the word begining. So, in a content search, bana* will find banana but *nana will NOT find banana. Am unsure if this is by design or if I am goofing somewhere. Could anyone please advise? Hello Ken, This is by design. Windows Search is now word-based and content searches work from left to right. Try searching on the whole word that contains the string and then add other criteria to filter the results by date, location, file extension or whatever is appropriate. Doug M. in NJ |
|
|||
Windows Search 4 - Wildcard in file content
On Tue, 22 Sep 2009 02:02:01 -0700, Ken-T
wrote: Have Windows Search 4 in use under XP pro. Works rather nicely - but - although I can use wildcards such as "*" for file names - use of wildcards for words contained in file content does not work for the word begining. So, in a content search, bana* will find banana but *nana will NOT find banana. Am unsure if this is by design or if I am goofing somewhere. Could anyone please advise? Hello Ken, This is by design. Windows Search is now word-based and content searches work from left to right. Try searching on the whole word that contains the string and then add other criteria to filter the results by date, location, file extension or whatever is appropriate. Doug M. in NJ |
|
|||
Windows Search 4 - Wildcard in file content
Hi Doug,
thanks for that. It's enough to know it was by design and that I was just not finding the right search format or something. This particular need for a wildcard couldn#t really be solved by ading to the search (unless you know of some methoid). In the docs were Mr.F.Jones (names changed to protect the innocent). Yes, the user created the docs with no space between..... so since nobody could remember the first name was tring for *jones mr*jones etc etc Anyway. Thanks. "Retroman" wrote: On Tue, 22 Sep 2009 02:02:01 -0700, Ken-T wrote: Have Windows Search 4 in use under XP pro. Works rather nicely - but - although I can use wildcards such as "*" for file names - use of wildcards for words contained in file content does not work for the word begining. So, in a content search, bana* will find banana but *nana will NOT find banana. Am unsure if this is by design or if I am goofing somewhere. Could anyone please advise? Hello Ken, This is by design. Windows Search is now word-based and content searches work from left to right. Try searching on the whole word that contains the string and then add other criteria to filter the results by date, location, file extension or whatever is appropriate. Doug M. in NJ |
|
|||
Windows Search 4 - Wildcard in file content
Hi Doug, thanks for that. It's enough to know it was by design and that I was just not finding the right search format or something. This particular need for a wildcard couldn#t really be solved by ading to the search (unless you know of some methoid). In the docs were Mr.F.Jones (names changed to protect the innocent). Yes, the user created the docs with no space between..... so since nobody could remember the first name was tring for *jones mr*jones etc etc Anyway. Thanks. "Retroman" wrote: On Tue, 22 Sep 2009 02:02:01 -0700, Ken-T wrote: Have Windows Search 4 in use under XP pro. Works rather nicely - but - although I can use wildcards such as "*" for file names - use of wildcards for words contained in file content does not work for the word begining. So, in a content search, bana* will find banana but *nana will NOT find banana. Am unsure if this is by design or if I am goofing somewhere. Could anyone please advise? Hello Ken, This is by design. Windows Search is now word-based and content searches work from left to right. Try searching on the whole word that contains the string and then add other criteria to filter the results by date, location, file extension or whatever is appropriate. Doug M. in NJ |
|
|||
Windows Search 4 - Wildcard in file content
On Tue, 22 Sep 2009 06:47:01 -0700, Ken-T
wrote: Hi Doug, thanks for that. It's enough to know it was by design and that I was just not finding the right search format or something. This particular need for a wildcard couldn#t really be solved by ading to the search (unless you know of some methoid). In the docs were Mr.F.Jones (names changed to protect the innocent). Yes, the user created the docs with no space between..... so since nobody could remember the first name was tring for *jones mr*jones etc etc Anyway. Thanks. Your quite welcome, Ken. In the example you give, did you try searching on simply "Jones" , with no wild cards? I would expect that to work. Text following a period should be interpreted as the start of a word. Doug M. in NJ |
|
|||
Windows Search 4 - Wildcard in file content
On Tue, 22 Sep 2009 06:47:01 -0700, Ken-T
wrote: Hi Doug, thanks for that. It's enough to know it was by design and that I was just not finding the right search format or something. This particular need for a wildcard couldn#t really be solved by ading to the search (unless you know of some methoid). In the docs were Mr.F.Jones (names changed to protect the innocent). Yes, the user created the docs with no space between..... so since nobody could remember the first name was tring for *jones mr*jones etc etc Anyway. Thanks. Your quite welcome, Ken. In the example you give, did you try searching on simply "Jones" , with no wild cards? I would expect that to work. Text following a period should be interpreted as the start of a word. Doug M. in NJ |
|
|||
Windows Search 4 - Wildcard in file content
Hi again,
yes, I did test for simply "jones" but there are no finds. (I suspected that some punctuation counts as a delimiter and found/used examples during tests, mainly for numbers). The odd thing is, if I test with a document containing mr,f,jones with commas instead of periods then yes, it finds "jones"! Erm.... any ideas? Thanks. Ken "Retroman" wrote: On Tue, 22 Sep 2009 06:47:01 -0700, Ken-T wrote: Hi Doug, thanks for that. It's enough to know it was by design and that I was just not finding the right search format or something. This particular need for a wildcard couldn#t really be solved by ading to the search (unless you know of some methoid). In the docs were Mr.F.Jones (names changed to protect the innocent). Yes, the user created the docs with no space between..... so since nobody could remember the first name was tring for *jones mr*jones etc etc Anyway. Thanks. Your quite welcome, Ken. In the example you give, did you try searching on simply "Jones" , with no wild cards? I would expect that to work. Text following a period should be interpreted as the start of a word. Doug M. in NJ |
|
|||
Windows Search 4 - Wildcard in file content
Hi again,
yes, I did test for simply "jones" but there are no finds. (I suspected that some punctuation counts as a delimiter and found/used examples during tests, mainly for numbers). The odd thing is, if I test with a document containing mr,f,jones with commas instead of periods then yes, it finds "jones"! Erm.... any ideas? Thanks. Ken "Retroman" wrote: On Tue, 22 Sep 2009 06:47:01 -0700, Ken-T wrote: Hi Doug, thanks for that. It's enough to know it was by design and that I was just not finding the right search format or something. This particular need for a wildcard couldn#t really be solved by ading to the search (unless you know of some methoid). In the docs were Mr.F.Jones (names changed to protect the innocent). Yes, the user created the docs with no space between..... so since nobody could remember the first name was tring for *jones mr*jones etc etc Anyway. Thanks. Your quite welcome, Ken. In the example you give, did you try searching on simply "Jones" , with no wild cards? I would expect that to work. Text following a period should be interpreted as the start of a word. Doug M. in NJ |
|
|||
Windows Search 4 - Wildcard in file content
File names are indexed forward and backward so *search and search* both
work, but not contents. -- .. -- "Ken-T" wrote in message ... Hi again, yes, I did test for simply "jones" but there are no finds. (I suspected that some punctuation counts as a delimiter and found/used examples during tests, mainly for numbers). The odd thing is, if I test with a document containing mr,f,jones with commas instead of periods then yes, it finds "jones"! Erm.... any ideas? Thanks. Ken "Retroman" wrote: On Tue, 22 Sep 2009 06:47:01 -0700, Ken-T wrote: Hi Doug, thanks for that. It's enough to know it was by design and that I was just not finding the right search format or something. This particular need for a wildcard couldn#t really be solved by ading to the search (unless you know of some methoid). In the docs were Mr.F.Jones (names changed to protect the innocent). Yes, the user created the docs with no space between..... so since nobody could remember the first name was tring for *jones mr*jones etc etc Anyway. Thanks. Your quite welcome, Ken. In the example you give, did you try searching on simply "Jones" , with no wild cards? I would expect that to work. Text following a period should be interpreted as the start of a word. Doug M. in NJ |
|
Thread Tools | |
Display Modes | |
|
|