File search fails when "Containing text:" parm used.

  • Thread starter Thread starter Tom Harris
  • Start date Start date
T

Tom Harris

When searching for text files of the filename form
backup*.log in their default directory, search succeeds
unless "Containing text:" parameter is used. This results
in no files to be found. Anybody know why? These files
are ascii, plain text. Nothing found in KB.
 
I did this little experiment:
- Paste the text from your post into c:\test.txt
- Click Start / Search
- Type "searching" into the box "Containing text"
- Type "c:\" into the box "Look in"
- Click "Search Now"

It found the text straight away. What do you get when
you run the same experiment?
 
Your experiment duplicates here exactly. Note the
specifics of the situation. "When searching ascii text
backup log files, inclusion of a string in the containing
text field causes files not to be found".
 
Sorry, I don't understand what you're saying. I don't even
know what you mean with "Your experiment duplicates here
exactly" - you do not explicitly say what the result of the
experiment was.

If you wish to continue this thread then you need to respond
rapidly, as you are about to disappear from the horizon of
my newsreader.
 
The problem appears to be that the backup logs are not ASCII, but Unicode.
The search function apparently does not recognize Unicode text strings
within the files it's search. I consider this a defect.

To demonstrate that the files are in fact coded in Unicode, open one with
Notepad, then click File, Save As. The option in the Encoding box will be
"Unicode". Change that to ASCII and save the file under a variant name.
You'll find that 1) the size of the file is reduced by 50%, and 2) search
containing text will find the new file.
 
Back
Top