Dica wrote:
> i've taken over a web app built by another developer. he was stripping out
> special characters and replacing with standard ones when searching our
> people table. for instance:
>
> "=E9" was replaced with "e". this seemed to work fine and would return na=
mes
> like 'Jose' as well as 'Jos=E9'. as a matter of fact, '=E9' doesn't even =
seem to
> be recognized as a statement like 'select * from people where lastName li=
ke
> '%=E9%' ' returns nothing. so, it seems like replacing =E9 for e is the r=
ight
> thing to do here.
>
> however, he was also replacing "=E3" with "a", but this character seems t=
o be
> different. if we replace "=E3" with "a", i get no matches when searching =
for a
> last name like "Sim=E3o".
>
> anybody know why some of these characters are ignored while others aren't?

"Damon" <damonf@cox.net> wrote in message
news:1153347237.900185.84620@p79g2000cwp.googlegroups.com...

Dica wrote:
> i've taken over a web app built by another developer. he was stripping out
> special characters and replacing with standard ones when searching our
> people table. for instance:
>
> "é" was replaced with "e". this seemed to work fine and would return names
> like 'Jose' as well as 'José'. as a matter of fact, 'é' doesn't even seem
> to
> be recognized as a statement like 'select * from people where lastName
> like
> '%é%' ' returns nothing. so, it seems like replacing é for e is the right
> thing to do here.
>
> however, he was also replacing "ã" with "a", but this character seems to
> be
> different. if we replace "ã" with "a", i get no matches when searching for
> a
> last name like "Simão".
>
> anybody know why some of these characters are ignored while others aren't?