Datatype error with trademark character

[Josh]

We have a field , defined as 'text' that causes a datatype error
qualification failure when the field contains the 0x99(T) character.
Data Type Error - FldObj(OBR_in) data type error
expected 'text' found 0xffffff99(T)
It does not fail on the production server which is 5.3.3.3 Windows 2000.
Concerned because we are testing some new Win2k3 servers for an upgrade to
5.5.3 and this would affect a multitude of interfaces. The obvious option is
to set the field to raw datatype but I would rather determine why this is
happening in case other fields are affected by as yet unknown characters.
This works on Windows 2000 , 5.3.3.3
Fails on Win XP SP3 , 5.3.3.3
Fails on Windows 2003 SP2 , 5.5.3
Has anyone seen anything like this before ?
Thanks,
Josh

[Rex Nufer]

You say this is 0x99? As in a hex 99? This value is not in the ascii
range. A capital 'T'
is a hex 54. Where is the value coming from? Is it in a test
transaction? If so, it's
possible you have a transaction with bad data in it. An embedded char
that shouldn't
be there.

[Josh]

0x99 in hex is the trademark character which displayed as a
T in my post , it looks like a very small 'TM'. I realize it
may not be in the normal text range but am wondering why it
passes as text on Win2k but not on XP or Win2k3.
Perhaps there is a system setting ?
Thanks

[Rex Nufer]

> > be there.- Hide quoted text -
>
> - Show quoted text -

I can't answer your question about a system setting or why
it works in one version of the OS but not the other. But I can
tell you we had this problem with other chars like the degree
char or the value 1/2 when passed as 1 char. None of these
chars are in the ascii range and therfore will not qual as
'text'. Like you said in your post, I think the only way around
it is to use the raw setting. Good luck.

[Josh]

FYI , I discovered that this does not affect the server and
only occurs on the client.