Control over how Global Search uses wildcards

Currently, the user has no control over how Global Search uses wildcards.  The behavior is different depending if you are using "regular" search or instant search:

-Using "regular" search (on non-instant search services), wildcards get appended before and after - eg  *search string*
-Using Instant Search, it seems to search each word independently, using only a trailing wildcard - eg  search* string*

If you search for "smith", global search will find "THE SMITHSONIAN", and "LOCKSMITH"
However, instant search will find "THE SMITHSONIAN", but WON'T find "LOCKSMITH"

At the very least, both search methods should return the same recordset.  Ideally, we'd have control over if/how wildcards are used.

Thanks,

Chris