Bill (SysAdmin) figured out that it'll choke on ticks (') or (`). I'm guessing it'll also choke on quotes (") or and per se & (&) or maybe even dashes (-) or less than (<) or greater than (>) and some others. That's predictable as those marks are DB commands.
The solution might be to just add a little explanation about how the search string is packaged for submission to the db search engine (which is MySQL via php, btw)
To escape ticks or other MySQL commands just use a backslash () before the questionable character. If it's not a command character, it'll only interpret the backslash to mean "take this literally, not as a command". So when in doubt, just backslash it.
There is so much in the bible against which every insinct of my being rebels, so much so that I regret the necessity which has compelled me to read it through from beginning to end. I do not think that the knowledge I have gained of its history and sources compensates me for the unpleasant details it has forced upon my attention.
--Helen Keller, American lecturer
_________________
Ginger Warbis ~ Antigen
Seed sibling `71 - `80
Straight South (Sarasota, FL)
10/80 - 10/82
Anonymity AnonymousSome days, it's just not worth chewing through the leather straps.
