Jacob Lund wrote:The correct solution might be to convert from UTF-8 to Unicode before
storing the data and then change the database scheme to Unicode char in all
fields containing strings.
Hmmmm. You might be confusing certain things here. On one side there is Unicode having a number for each character. On the other side there is the representation in bytes. Now, UTF-8 *is* Unicode, but on the other side, i.e. the representation in bytes. Thus it does not make too much sense to compare Unicode with UTF-8. Do you agree?
A lot of microsoft's documentation confusingly uses "unicode" when it actually means "UTF-16" or "UCS-2" (I can never remember what the difference between those two is, and I don't know if it matters). I suspect rereading Jacob's mail mentally substituting "UTF-16" for "unicode" will make it clearer.
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
