Classic ASP ODBC 3.51 UTF8 problem

Hi,

I have been asked to convert an Australian web site to handle Chinese
characters. It has a MySQL 5.0 database and has a front end written in
ASP.NET VB V1.1 and a CMS written in Classic ASP. I seem to have been
successful in converting the database to UTF-8 and the .NET application =
as
various extended characters can be input via forms and read back on the =
web
pages.

I should also say that all pages are XHTML.

My problem comes with the CMS, it neither reads back nor inputs =
correctly
any extended characters (=F8, =E5, etc). The pages are using the same =
database
tables as the .NET front end and have response.charset=3D"utf-8" in each =
of
them plus the content/type meta tag charset=3DUTF-8 set ok. It appears =
to me
that the ODBC connector isn't carrying the encoding correctly.

The .NET connection string: "Driver=3D{MySQL ODBC 3.51 Driver};
Server=3Dlocalhost; Port=3D3306; UID=3DtheDB; PWD=3Dxxxxxxxx; =
charset=3Dutf8;
OPTION=3D3; Database=3Ddaelive"

The Classic ASP connection string: "Driver=3D{MySQL ODBC 3.51 Driver};
Server=3Dlocalhost; Port=3D3306; UID=3DtheDB; PWD=3D xxxxxxxx; character =
set=3Dutf8;
OPTION=3D3; Database=3Dconfig"

I've added the "charset=3Dutf8" and "character set=3Dutf8" from the =
results of a
lot of Googling so I'm not positive they are correct.

Could someone please advise as I'm VERY new to MySQL. I'm not even sure =
that
the non-.NET ODBC driver can handle utf-8 properly.

Best regards,

Craig Stevens
The Incredibly Useful Company Limited
craig@incrediblyuseful.net
Tel: +44 (0)1753 573510
Fax: +44 (0)870 130 3707
Skype: callto://craig1001
=20


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg

RE: Classic ASP ODBC 3.51 UTF8 problem

I have failed miserably trying the same task as you. I'm using MS Access as
the front end. It can handle Chinese characters locally, but it cannot
through the MySQL ODBC driver even though you can set the connection
character set to utf8. The reason your other applications work is probably
that they don't use ODBC.

I've gotten conflicting responses to my questions here. It might be that
version 4 of the ODBC connector will handle this.

Regards,

Jerry Schwartz
The Infoshop by Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032

860.674.8796 / FAX: 860.674.8341

www.the-infoshop.com
www.giiexpress.com
www.etudes-marche.com


> -----Original Message-----
> From: Craig [mailto:craig@incrediblyuseful.net]
> Sent: Thursday, July 26, 2007 10:00 AM
> To: myodbc@lists.mysql.com
> Subject: Classic ASP ODBC 3.51 UTF8 problem
>
> Hi,
>
> I have been asked to convert an Australian web site to handle Chinese
> characters. It has a MySQL 5.0 database and has a front end
> written in
> ASP.NET VB V1.1 and a CMS written in Classic ASP. I seem to have been
> successful in converting the database to UTF-8 and the .NET
> application as
> various extended characters can be input via forms and read
> back on the web
> pages.
>
> I should also say that all pages are XHTML.
>
> My problem comes with the CMS, it neither reads back nor
> inputs correctly
> any extended characters (ø, å, etc). The pages are using the
> same database
> tables as the .NET front end and have
> response.charset="utf-8" in each of
> them plus the content/type meta tag charset=UTF-8 set ok. It
> appears to me
> that the ODBC connector isn't carrying the encoding correctly.
>
> The .NET connection string: "Driver={MySQL ODBC 3.51 Driver};
> Server=localhost; Port=3306; UID=theDB; PWD=xxxxxxxx; charset=utf8;
> OPTION=3; Database=daelive"
>
> The Classic ASP connection string: "Driver={MySQL ODBC 3.51 Driver};
> Server=localhost; Port=3306; UID=theDB; PWD= xxxxxxxx;
> character set=utf8;
> OPTION=3; Database=config"
>
> I've added the "charset=utf8" and "character set=utf8" from
> the results of a
> lot of Googling so I'm not positive they are correct.
>
> Could someone please advise as I'm VERY new to MySQL. I'm not
> even sure that
> the non-.NET ODBC driver can handle utf-8 properly.
>
> Best regards,
>
> Craig Stevens
> The Incredibly Useful Company Limited
> craig@incrediblyuseful.net
> Tel: +44 (0)1753 573510
> Fax: +44 (0)870 130 3707
> Skype: callto://craig1001
>
>
>
> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe: http://lists.mysql.com/myodbc?unsub=jerry@gii.co.jp
>
>




--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org

RE: Classic ASP ODBC 3.51 UTF8 problem

Thanks Jerry,

One of my issues is that I need someone to tell me if I got the =
connection
strings right. Is it correct that the .NET connector uses =
"charset=3Dutf8"
and the ODBC one uses "character set=3Dutf8"? I'd really like some =
confidence
to be able to face my client. Is there any documentation on this =
anywhere as
I can't find it, it's all rumour and hearsay.

Cheers,

Craig Stevens
The Incredibly Useful Company Limited
craig@incrediblyuseful.net
Tel: +44 (0)1753 573510
Fax: +44 (0)870 130 3707
Skype: callto://craig1001
=20

-----Original Message-----
From: Jerry Schwartz [mailto:jerry@gii.co.jp]=20
Sent: 26 July 2007 16:00
To: craig@incrediblyuseful.net; myodbc@lists.mysql.com
Subject: RE: Classic ASP ODBC 3.51 UTF8 problem

I have failed miserably trying the same task as you. I'm using MS Access =
as
the front end. It can handle Chinese characters locally, but it cannot
through the MySQL ODBC driver even though you can set the connection
character set to utf8. The reason your other applications work is =
probably
that they don't use ODBC.

I've gotten conflicting responses to my questions here. It might be that
version 4 of the ODBC connector will handle this.

Regards,

Jerry Schwartz
The Infoshop by Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032

860.674.8796 / FAX: 860.674.8341

www.the-infoshop.com
www.giiexpress.com
www.etudes-marche.com


> -----Original Message-----
> From: Craig [mailto:craig@incrediblyuseful.net]
> Sent: Thursday, July 26, 2007 10:00 AM
> To: myodbc@lists.mysql.com
> Subject: Classic ASP ODBC 3.51 UTF8 problem
>
> Hi,
>
> I have been asked to convert an Australian web site to handle Chinese
> characters. It has a MySQL 5.0 database and has a front end
> written in
> ASP.NET VB V1.1 and a CMS written in Classic ASP. I seem to have been
> successful in converting the database to UTF-8 and the .NET
> application as
> various extended characters can be input via forms and read
> back on the web
> pages.
>
> I should also say that all pages are XHTML.
>
> My problem comes with the CMS, it neither reads back nor
> inputs correctly
> any extended characters (=F8, =E5, etc). The pages are using the
> same database
> tables as the .NET front end and have
> response.charset=3D"utf-8" in each of
> them plus the content/type meta tag charset=3DUTF-8 set ok. It
> appears to me
> that the ODBC connector isn't carrying the encoding correctly.
>
> The .NET connection string: "Driver=3D{MySQL ODBC 3.51 Driver};
> Server=3Dlocalhost; Port=3D3306; UID=3DtheDB; PWD=3Dxxxxxxxx; =
charset=3Dutf8;
> OPTION=3D3; Database=3Ddaelive"
>
> The Classic ASP connection string: "Driver=3D{MySQL ODBC 3.51 Driver};
> Server=3Dlocalhost; Port=3D3306; UID=3DtheDB; PWD=3D xxxxxxxx;
> character set=3Dutf8;
> OPTION=3D3; Database=3Dconfig"
>
> I've added the "charset=3Dutf8" and "character set=3Dutf8" from
> the results of a
> lot of Googling so I'm not positive they are correct.
>
> Could someone please advise as I'm VERY new to MySQL. I'm not
> even sure that
> the non-.NET ODBC driver can handle utf-8 properly.
>
> Best regards,
>
> Craig Stevens
> The Incredibly Useful Company Limited
> craig@incrediblyuseful.net
> Tel: +44 (0)1753 573510
> Fax: +44 (0)870 130 3707
> Skype: callto://craig1001
>
>
>
> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe: =
http://lists.mysql.com/myodbc?unsub=3Djerry@gii.co.jp
>
>




--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc@m.gmane.o rg

RE: Classic ASP ODBC 3.51 UTF8 problem

Yes, it is all rumor or hearsay, except I think some of what I remember came
from a MySQL AB representative in this forum.

Regards,

Jerry Schwartz
The Infoshop by Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032

860.674.8796 / FAX: 860.674.8341

www.the-infoshop.com
www.giiexpress.com
www.etudes-marche.com


> -----Original Message-----
> From: Craig [mailto:craig@incrediblyuseful.net]
> Sent: Thursday, July 26, 2007 12:48 PM
> To: myodbc@lists.mysql.com; 'Jerry Schwartz'
> Subject: RE: Classic ASP ODBC 3.51 UTF8 problem
>
> Thanks Jerry,
>
> One of my issues is that I need someone to tell me if I got
> the connection
> strings right. Is it correct that the .NET connector uses
> "charset=utf8"
> and the ODBC one uses "character set=utf8"? I'd really like
> some confidence
> to be able to face my client. Is there any documentation on
> this anywhere as
> I can't find it, it's all rumour and hearsay.
>
> Cheers,
>
> Craig Stevens
> The Incredibly Useful Company Limited
> craig@incrediblyuseful.net
> Tel: +44 (0)1753 573510
> Fax: +44 (0)870 130 3707
> Skype: callto://craig1001
>
>
> -----Original Message-----
> From: Jerry Schwartz [mailto:jerry@gii.co.jp]
> Sent: 26 July 2007 16:00
> To: craig@incrediblyuseful.net; myodbc@lists.mysql.com
> Subject: RE: Classic ASP ODBC 3.51 UTF8 problem
>
> I have failed miserably trying the same task as you. I'm
> using MS Access as
> the front end. It can handle Chinese characters locally, but it cannot
> through the MySQL ODBC driver even though you can set the connection
> character set to utf8. The reason your other applications
> work is probably
> that they don't use ODBC.
>
> I've gotten conflicting responses to my questions here. It
> might be that
> version 4 of the ODBC connector will handle this.
>
> Regards,
>
> Jerry Schwartz
> The Infoshop by Global Information Incorporated
> 195 Farmington Ave.
> Farmington, CT 06032
>
> 860.674.8796 / FAX: 860.674.8341
>
> www.the-infoshop.com
> www.giiexpress.com
> www.etudes-marche.com
>
>
> > -----Original Message-----
> > From: Craig [mailto:craig@incrediblyuseful.net]
> > Sent: Thursday, July 26, 2007 10:00 AM
> > To: myodbc@lists.mysql.com
> > Subject: Classic ASP ODBC 3.51 UTF8 problem
> >
> > Hi,
> >
> > I have been asked to convert an Australian web site to
> handle Chinese
> > characters. It has a MySQL 5.0 database and has a front end
> > written in
> > ASP.NET VB V1.1 and a CMS written in Classic ASP. I seem
> to have been
> > successful in converting the database to UTF-8 and the .NET
> > application as
> > various extended characters can be input via forms and read
> > back on the web
> > pages.
> >
> > I should also say that all pages are XHTML.
> >
> > My problem comes with the CMS, it neither reads back nor
> > inputs correctly
> > any extended characters (ø, å, etc). The pages are using the
> > same database
> > tables as the .NET front end and have
> > response.charset="utf-8" in each of
> > them plus the content/type meta tag charset=UTF-8 set ok. It
> > appears to me
> > that the ODBC connector isn't carrying the encoding correctly.
> >
> > The .NET connection string: "Driver={MySQL ODBC 3.51 Driver};
> > Server=localhost; Port=3306; UID=theDB; PWD=xxxxxxxx; charset=utf8;
> > OPTION=3; Database=daelive"
> >
> > The Classic ASP connection string: "Driver={MySQL ODBC 3.51 Driver};
> > Server=localhost; Port=3306; UID=theDB; PWD= xxxxxxxx;
> > character set=utf8;
> > OPTION=3; Database=config"
> >
> > I've added the "charset=utf8" and "character set=utf8" from
> > the results of a
> > lot of Googling so I'm not positive they are correct.
> >
> > Could someone please advise as I'm VERY new to MySQL. I'm not
> > even sure that
> > the non-.NET ODBC driver can handle utf-8 properly.
> >
> > Best regards,
> >
> > Craig Stevens
> > The Incredibly Useful Company Limited
> > craig@incrediblyuseful.net
> > Tel: +44 (0)1753 573510
> > Fax: +44 (0)870 130 3707
> > Skype: callto://craig1001
> >
> >
> >
> > --
> > MySQL ODBC Mailing List
> > For list archives: http://lists.mysql.com/myodbc
> > To unsubscribe:
> http://lists.mysql.com/myodbc?unsub=jerry@gii.co.jp
> >
> >
>
>
>
>




--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org