The search was changed to use full-text indexing about a week after the site redesign. The previous search did use the "... LIKE '%...%'" method but was becoming far too slow (and too intensive on the server - making all of P2P slow). The search now uses "contains(...)" The advantage is that the search completes in seconds, rather than sometimes timing out after a minute.

The side-effect is that the full-text search breaks words on non-letter/number characters. The search function has to filter out common "noise" words (a, and, or, etc.) and characters that break the search (this is what happygv was seeing when searching for things that contained characters like <, /, etc.).

The underscore in your search is probably being filtered strangely. I'll look into it to see if there's a work-around.

What I really need is the "official" list of characters that are allowed as a search phrase for the contains() statement in SQL Server.

Bruce Luckcuck
Director, Applications & Support Services
Wiley Publishing, Inc.