<div>
After digging through several newsgroups, I found a fix: &nbsp;Changing the charset of my ODBC DSN to iso_1.<br />
<br />
Admin, please close out this question.<br />
<br />
Thanks!
</div>


After digging through several newsgroups, I found a fix:  Changing the charset of my ODBC DSN to iso_1.

Admin, please close out this question.

Thanks!

<div>
Please post to the Community Support TA and ask for a refund.
</div>


Please post to the Community Support TA and ask for a refund.

<div>
<div class="content wysiwyg-content">
I have a Visual Basic (6.0 SP6) application using ADO (2.7) to connect to a Sybase database (12.5). &nbsp;The application recently upgraded to be run on a Windows XP (SP1) environment, using the Sybase ODBC 5.00.00.56 driver. &nbsp; Doing a regular SELECT statement, if the field contains an extended character, for example: café, when I look at the ADO Recordset, the text comes back as cafÅ.<br />
<br />
We did not have this problem running the same application on Windows 2000, using Sybase ODBC driver 3.60.00.21.<br />
<br />
People are saying that it's a codeset issue, but I'm thinking it's an ODBC driver issue. &nbsp; Has anyone faced this issue before, and what can be done to resolve it?<br />
<br />
The worst case scenario is that I force the text to convert the extended characters properly, but that's the last thing I want to do.<br />
<br />
Thanks in advance,<br />
Robert<br />

</div>
</div>


I have a Visual Basic (6.0 SP6) application using ADO (2.7) to connect to a Sybase database (12.5).  The application recently upgraded to be run on a Windows XP (SP1) environment, using the Sybase ODBC 5.00.00.56 driver.   Doing a regular SELECT statement, if the field contains an extended character, for example: café, when I look at the ADO Recordset, the text comes back as cafÅ.

We did not have this problem running the same application on Windows 2000, using Sybase ODBC driver 3.60.00.21.

People are saying that it's a codeset issue, but I'm thinking it's an ODBC driver issue.   Has anyone faced this issue before, and what can be done to resolve it?

The worst case scenario is that I force the text to convert the extended characters properly, but that's the last thing I want to do.

Thanks in advance,
Robert


Extended characters not translated properly using ADO

Sybase, a subsidiary of SAP, builds a client/server relational database management system. Products include Adaptive Server Enterprise (ASE), Adaptive Server Anywhere (ASA), Sybase Unwired Platform (SUP) for mobile applications, Afaria for enterprise mobile device management and IQ for data warehouse and big data applications.