[Mike Irwin]

It searches 1 word fine.

It chokes BIG time on two words. Dies. Blows up. etc.

[tyme]

Hmm.. looks more or less okay to me. If "dies" means "says there are no search results," well, that's life. Not every question has an answer. :p

[Mike Irwin]

Tyme,

No, sorry, should have been more descriptive.

As in dies, I mean the status bar says "Done" at the bottom, and it returns a BLANK screen.

No THR header, no results, no "Sorry, DumbA@@, your search results came up zip..." just a completely blank screen.

[tyme]

Does this happen all the time, some of the time, or very rarely? Or only with certain words? If so, can you give an example?

I don't seem to be able to duplicate what you're describing.

[Mike Irwin]

Tyme,

This was happening to me ALL of the time on Friday when I first attempted to do my search, both at my office at at home. I have high-speed internet both places.

My search terms were "Hornady" and "AP*" which, unless I'm missing something, should have returned threads on the Hornady AP.

Using a single search term, Hornady or AP* resulted in a very fast search with lots of appropriate hits.

AP* wasn't as effective, obviously, as I'd get all sorts of hits for words that started with AP and a third character (apprehensive, apparent, etc.).

I tried the dual keyword search both in just Handloading and also in an overall site search.

No matter what, using the two keywords, it returned the screen that I described.

I've not tried it again since then, however, but I'm going to do so now, and I'll report back.

[Mike Irwin]

No joy.

Double keyword searchs with the * wildcard are still returning the blank screen.

I just realized something, too.

When I do this search, I don't even get the "Your search is in progress" screen, it grinds for about 30 seconds, then goes straight to a completely blank screen.

Using the single key word results in a very fast search with a page of results.

The * wildcard also gives results, but it's slower, which I think should be obvious.

And I think I just figured it out.

I just tried a search using two complete terms -- not a term and a wildcard.

It resulted in a fast search with pertinent results.

The problem is apparently when attempting to use one complete keyword and a wildcard.

[Mal H]

Interesting. I'm getting the same result as Mike using "Hornady AP*" - a blank 'Done' screen. However, when I reverse the keywords, i.e., "AP* Hornady" the search works. I tried it both ways several times and the results are consistent. When I get the blank screen it is not preceeded by the notice "Search in progress. Your results will be returned shortly" or whatever it says. Sure looks like a vB search engine bug to me, probably not much we can do from our end.