Probably due to the search page being poorly coded. Apostrophes, if they're not escaped, can produce unintended behavior when dropped into an SQL query since SQL uses apostrophes to denote the beginnings and ends of string values.
As a workaround, you can search for a sub-string, like "haven" instead of "haven't" and you should get similar results.
__________________ Quote: |
Originally Posted by tomokosasaki GOLD will come with 2nd conclusion!! Just have some trust. I can't always tell my source! But, in the end, you'll see i was right and this conversation won't matter anymore. | |