"pcartier" wrote:
> I have just tried your searchstring type:*.doc
> option and I am sorry to say it does not turn up anything in a test
> directoy which I KNOW has certain files with certain content. I have just tried
> it with simple .txt files and a more obscure file type with extension
> .inc. Neither worked. I had limited success last night with searchstring ext:doc
> also tried searchstring name*.doc without success.
Where are the files? Is this an indexed location? These searches should
work properly. Try just doing a search for * and seeing if the files come
back. Please take a look at
http://support.microsoft.com/kb/932989/en-us for
reasons the file might not be found. Also, please take a look at
http://msdn.microsoft.com/en-us/library/bb266512.aspx for reference about the
AQS search syntax.
> I have seen several negative comments about this search engine and all
> I really need to know is if it is actually stable. If so I am doing
> something wrong! Otherwise I shall just switch to a 3rd party desktop
> searcher ...
There are some occaisional reliability issues that are known in the indexer
that are being addressed in Windows Search 4. It is currently available as a
Beta release on download center. You should see far less indexing
reliability issues in that release. This release is only about searching in
indexed locations.
I haven't determined if the issue is related to this sort of reliability
issue or not. If the item is not being returned in any search (try searching
for * in the folder containing the item), this may be the issue.
Otherwise, it is likely confusion about what the system is trying to do
versus what you're trying to do. Answers to other questions I've posed will
help straighten this out.
> OH.... and I checked ... the Search options for the directory inn
> question does have "search file names and contents" checked...
Search options are per-system, not per-location. You should not see the
"Search in file contents" button unless you're not currently searching the
file contents due to your search options. The default is to only search file
contents in indexed locations, as searching contents is an intensive
operation on non-indexed items.
> Also: it appears that even if I get this stuff to work I cannot
> differentiate between a text search and a file name search ... AM I
> CORRECT HERE TOO ?
You can using the "contents:" property. Unfortunately, this syntax only
works on indexed searches.
> --
> pcartier
> Posted via http://www.vistaheads.com
>
>