Unicode characters getting automatically substituted to nearest match

Question

1.00/5 (1 vote)

See more:

Vb6 application is connected to Sql server via ODBC, and for some users, the Unicode Characters which are stored in the database, having å, ä, ö chars in them.
while a query is fired which gets this column values, they are substituted by
a, a, o.. and for some other users in a different location, it works fine and they donot get converted.

Possible ODBC configuration setting is set: "Translate Character Data: Yes"

Any reason where this auto conversion could be configured. I tried changing the client Locale, but it doesnt convert the chars.. I want the chars NOT to be converted.

Posted 18-Jun-13 5:36am

Mubeen.asim

Updated 18-Jun-13 6:37am

RedDk

v3

Add a Solution

Comments

Sergey Alexandrovich Kryukov 18-Jun-13 12:13pm

VB6? You cannot be serious. It cannot not fully support Unicode. I would say, it cannot support programming. Is there any particular reason to suffer from this trash?
—SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Mubeen.asim · Answer 1 · 2013-06-18T21:07:00

Solution 1

This kind of problem occurs when there is a mismatch between the code page used by the SQL server and the client..

More detailed article can be found here

and try disabling the Automatic ANSI to OEM conversion from c:\Windows\system32\cliconfg.exe under the DB-Library options.

Posted 18-Jun-13 21:07pm

Mubeen.asim