Sign in with
Sign up | Sign in
Your question

Windows find function non-consistent

Tags:
  • Windows XP
Last response: in Windows XP
Share
Anonymous
March 17, 2005 5:27:03 AM

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

Out of a large number of files of the type csv, I want to make use of the
standard "Find file" function that comes with Windows. This is to allow me to
locate which file(s) contains a certain piece of text. A very handy piece of
tools, I agree. (I can call out the function normally by typing control-F,
after openin up a folder with Windows Explorer.

If I copy these large number of files onto different Window xp machines, why
the "search for files" function yield so much different results. Also, my csv
file has columns separated by the standard comma character. I can open all
the files quickly by selecting file, using standard MS Excel. Athough I
encounter no problem to open any one of these files this way, I need this
handy method to find my files for other purposes.

Question 1: why dfferent machines response to the same windows function
differently,

1) on one xp machine, the find function can locate the file all the time
2) on the second machine, the first find always fails. But if I repeat using
the "find" function the second time, it could normally find it.
3) on the third machine (all machines run windows xp Professopma;), I could
never be successful in order to locate the file containing certain piece of
text.

Can someone explain the irrregularities in the "FIND" function, given all
are windows xp machines? This is question 1.

Second question, what if the files has a "non-text" character as delimitor
(such as char asccii value = 240 ? Will it affect whether the find function
will work. I've tested it but it never works. do I miss out anything?

Third question. If the record delimitor for all these files is s a line feed
character only, not the stanard line feed and carrige return character, will
the Windows Find function still work?.

More about : windows find function consistent

Anonymous
March 17, 2005 11:10:33 AM

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

Create this registry file and run it to change the default search behavior Search will usually only look for text inside of files
with a registered filetype association
---search_all_files.reg---
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\*]
@="{5e941d80-bf96-11cd-b579-08002b30bfeb}"

--cut here--

--

Mark L. Ferguson (NOT an MS-MVP)
FAQ for MS Antispyware version 1.0.509
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
marfers notes for windows xp http://www.geocities.com/marfer_mvp/chatNotes.htm
..
"ykffc" <ykffc@discussions.microsoft.com> wrote in message news:26DFCDB9-45D3-4D35-931C-EC314E5DE7A9@microsoft.com...
> Out of a large number of files of the type csv, I want to make use of the
> standard "Find file" function that comes with Windows. This is to allow me to
> locate which file(s) contains a certain piece of text. A very handy piece of
> tools, I agree. (I can call out the function normally by typing control-F,
> after openin up a folder with Windows Explorer.
>
> If I copy these large number of files onto different Window xp machines, why
> the "search for files" function yield so much different results. Also, my csv
> file has columns separated by the standard comma character. I can open all
> the files quickly by selecting file, using standard MS Excel. Athough I
> encounter no problem to open any one of these files this way, I need this
> handy method to find my files for other purposes.
>
> Question 1: why dfferent machines response to the same windows function
> differently,
>
> 1) on one xp machine, the find function can locate the file all the time
> 2) on the second machine, the first find always fails. But if I repeat using
> the "find" function the second time, it could normally find it.
> 3) on the third machine (all machines run windows xp Professopma;), I could
> never be successful in order to locate the file containing certain piece of
> text.
>
> Can someone explain the irrregularities in the "FIND" function, given all
> are windows xp machines? This is question 1.
>
> Second question, what if the files has a "non-text" character as delimitor
> (such as char asccii value = 240 ? Will it affect whether the find function
> will work. I've tested it but it never works. do I miss out anything?
>
> Third question. If the record delimitor for all these files is s a line feed
> character only, not the stanard line feed and carrige return character, will
> the Windows Find function still work?.
>
!