I thought perhaps it was a font issue, but I verified that the font is
available on the server, that the character codes are the same, and
that the sql character set is the same in both places.
I'm sure this is covered somewhere, but I've been unable to form a
proper query in google to come up with an answer.
I'm using ASP.NET C# 2.0x, running on IIS 6
Any help is greatly appreciated.
thanks,
g
I can't see how fonts could have anything to do with it. My guess is
that in moving the code over you've changed it to:
string[] strVarArr = strVar.Split('');
--
Jon Skeet - <sk...@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
Is this the actual code you're using or demo code?
i.e. Is the code on your server really using 'x' as the parameter or
is it obtaining it from somewhere else?
It is a literal character in the split statement (using single
quotation marks). The actual character is "¶". (U+00B6 or "pilcrow
sign" in window's character map).
How are you representing that in the code?
like this...
string[] strVarArr = strVar.Split('¶');
in your original reply, you mentioned that maybe the character wasn't
there on the server, but the error message actually displays the
character when it's telling me that there's no character.
thanks.
g
It could well be an encoding issue. I suggest you use:
string[] strVarArr = strVar.Split('\u00b6');
--
Jon Skeet - <sk...@pobox.com>
I'll try that. I thought about it, but didn't know the syntax. I'll
reply after I give it a shot.
txs.
thanks much. it worked. not that it matters at this point, but why do
you suppose that would happen even though it had the same character
code on both machines?
Different machines may have different default encodings. In general,
embedding non-ascii characters directly in source code is a problem
waiting to happen.
--
Jon Skeet - <sk...@pobox.com>