|
No results at all with this approach, but thanks.
|
|
|
|
|
Is your location indexed?
|
|
|
|
|
Nope. Haven't cared for the overhead of the indexers in the past so I tend to avoid them.
Of course, there's always the old standby: cmd.
|
|
|
|
|
The win7 indexer is actually smart enough to only run when you're not not using the computer. The XP version always ended up curbstomped within a few weeks for stopping me from being able to work; it was as bad as diskkeeper in that regard. The win7 one I've never noticed running at all.
3x12=36
2x12=24
1x12=12
0x12=18
|
|
|
|
|
I've had similar problems with no results at all, indexed or not. In my case it was something to do with junctions that it didn't like I think.
I had my C:\Users junctioned to H:\Junction\Users and the search bar in Explorer within the documents library wouldn't work at all, but it does work if I manually navigate into H:\Junctions\Users and search in there.
|
|
|
|
|
That worked great. Thanks for the tip! Kind of a pain to have to type that many additional characters but, at least is works.
Being smarter than you look always beats looking smarter than you are.
|
|
|
|
|
Does it work if you surround the search criteria in quotes: "*.ascx*" ?
|
|
|
|
|
It does, but you'd better prefix it with name:, otherwise it will also search content.
|
|
|
|
|
Sound advice for a happier search experience!
|
|
|
|
|
Nope. No results at all with the quotes.
|
|
|
|
|
Weird. Worked for me.
Actually, it doesn't bloody work for me at all. That's having interpreted what you wrote and what you actually meant, of course.
|
|
|
|
|
Apparently it needs to be indexed. Leave it to MS to require jumping through a hoop that's been set on fire in order to do something as common as searching for files.
|
|
|
|
|
|
That looks handy, though I'm philosophically opposed to installing a utility just so I can search the file system. I may get over that objection, but geez! And they wonder why everyone hated Vista, or anything that smelled like it!
|
|
|
|
|
Once you dump Windows Explorer, the rest is easy.
|
|
|
|
|
Yeah I think the same way. Especially since I'm guessing there's loads of overhead in the background to do all this indexing etc and it's a shame if it's not even going to be used.
I guess there's some way to switch it off though - it was indexing service in earlier versions of windows, plus that stupid find fast thing that office insisted on installing even when you told it not to in the setup. Might have changed now.
|
|
|
|
|
All right folks, let's not leave you all in the dark: RTFM![^] 
|
|
|
|
|
Not to appear dense (though that may be unavoidable), but I'm not seeing a solution in the FM.
|
|
|
|
|
May I have misguided you a bit (didn't read the FM myself). Syntax would be for example for finding all files with the (old dos syntax) *.bat* -> filename:*.bat*
By the same token filename:???.bat will find all three-letter batch files.
Quotes are not really needed, except when keywords would appear in the search string.
I used to use name:, but filename: does not give me extraneous results.
Works fine on my system!
|
|
|
|
|
Obviously, you failed to enter the query properly. You need to use the new Microsoft Search dialect, that has been greatly improved, with more features and power through its simplified search syntax. So all you had to type was ...
Kind:Any Subject:Any Contains:Everything Author:Christopher Duncan || Lord Vader Date:> Today - Yesterday + Tomorrow * 356 - 12 + 1 Folders: All
I mean really. Get with the program.
|
|
|
|
|
I've got blisters on my fingers!
|
|
|
|
|
did you use appropriate technology to search the FM? e.g. did you index it?
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
|
|
|
|
|
A whole effing sparse B-Tree 
|
|
|
|
|
I was thinking of borrowing Christian's iPad. Maybe that's a technology that would work.
|
|
|
|
|
Have you tried leaving the star out, i.e.:
.ascx
|
|
|
|