Find on Click: search for files with two words

[kL13nT]

I am sure that the answer to this query will be simple. I am trying to search for a file that has two separate strings in the filename (e.g. music register list.doc) When I search using two strings (e.g. *music* OR *register*) I get a list of all files that contain either of the words (e.g. music.doc, medical register.xls, etc). Is there a way to perform the search so that I only get files with both search strings?

[Dave Wilkins]

You'd think so, wouldn't you? Actually, I never knew you could use OR (never needed it, never tried it). But AND doesn't seem to work, does it? I'll pass it to the developers...

[Dave Wilkins]

PS occurs to me it may have been left out because you can of course use

music*register

or even

music*list

to find

music course register (1st key)
or
music register list (both keys)

but it would fail on

Register of music.txt

(i.e. anything with the words in the wrong order). But it may help in the meantime. Note that you don't need to always include a * at beginning and end of your search terms - it's assumed in the code, so much so that

tore

will find both store.txt & tore.txt

If you want to find only the latter (disable the assumed asterisks), then use 'tore'

[kL13nT]

Thank you very much for the help. Interestingly, when I use music*register, I don't get any results at all. In order to make the search work, I find that I have to search for *music*register*.

Not sure if this is the intended functionality, but I would certainly prefer to be able to search for music*register and have FOC assume the leading and trailing '*'s.

[Dave Wilkins]

Strange...which version of FindOnClick are you using (program title bar should show you)?

Incidentally, the developer confirms AND (or equivalent) simply isn't supported. It's been added to the to-do list, but it's a long list...

[kL13nT]

I am using FOC v2.0.4.4.

I found this behaviour strange as well. I thought is might be that the filename in question actually has more strings in it (e.g. music list register summary.doc). I changed the search string to music*summary, and FOC still returns no results. I have to search for *music*summary* to get any results.

[Dave Wilkins]

Got it (I can replicate). I think using a wild-card in the middle must suppress the 'assumed' wildcards at the end somehow. I've reported it to the developer in case it's unintentional (but if so, don't hold your breath, as before). But there may be some deep technical reason...