UTF-8

------=_NextPart_000_13EA_01C7B9A2.5F2C2E80
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

Did I read somewhere that ODBC 3.x doesn't support UTF-8? We're trying to
display Chinese characters in MS Access. The characters are there in the
MySQL data base, and display just fine using our web-based applications, but
our goal is to allow our users to use MS Access for ad hoc queries.

Currently, no matter what I've tried, all I ever see is garbage. Will ODBC 5
resolve this? Does anyone have any ideas?

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


------=_NextPart_000_13EA_01C7B9A2.5F2C2E80--

Re: UTF-8

FYR, I use MyODBC 3.51.12 with Visual FoxPro 9 and MySQL 5.0.41 in
Traditional Chinese Windows XP pro, tables like below example are
working fine. Chinese data are displayed normal in VFP aplication and
Command Line Client, but garbage in MySQL Query Browser.


mysql> SHOW CREATE TABLE dsleger\G
*************************** 1. row ***************************
Table: dsleger
Create Table: CREATE TABLE `dsleger` (
`recnbr` int(10) unsigned NOT NULL auto_increment,
`no` varchar(12) collate latin1_bin default NULL,
`code` varchar(12) collate latin1_bin default NULL,
`acc` varchar(20) collate latin1_bin default NULL,
`nbr` decimal(8,2) default NULL,
`price` decimal(9,2) default NULL,
`i_basic` char(4) collate latin1_bin default NULL,
`desc` varchar(52) collate latin1_bin default NULL,
`dc` char(1) collate latin1_bin default NULL,
`amount` decimal(12,2) default NULL,
`rmk` varchar(512) collate latin1_bin default NULL,
PRIMARY KEY (`recnbr`),
KEY `I_no` (`no`(10)),
KEY `I_code` (`code`),
KEY `I_desc` (`desc`)
) ENGINE=MyISAM AUTO_INCREMENT=31528 DEFAULT CHARSET=latin1
COLLATE=latin1_bin COMMENT='DetailSleger'
1 row in set (0.00 sec)



Jerry Schwartz wrote:
> Did I read somewhere that ODBC 3.x doesn't support UTF-8? We're trying to
> display Chinese characters in MS Access. The characters are there in the
> MySQL data base, and display just fine using our web-based applications, but
> our goal is to allow our users to use MS Access for ad hoc queries.
>
> Currently, no matter what I've tried, all I ever see is garbage. Will ODBC 5
> resolve this? Does anyone have any ideas?
>
> 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
>
>


--
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: UTF-8

Thanks for the response. It is rather disappointing, because if I understand
you correctly then MS Access might be the problem.

One of my coworkers is using Chinese XP (I'm not sure if it is traditional
or not), and I think he has the Chinese version of MS Access. I will have to
double-check with him, and see if there is anything he can change on his end
that makes this work.

Do you have any suggestions?

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: Dennis Yu [mailto:service@dennisyu.idv.tw]
> Sent: Friday, June 29, 2007 2:04 AM
> To: Jerry Schwartz
> Cc: myodbc@lists.mysql.com
> Subject: Re: UTF-8
>
> FYR, I use MyODBC 3.51.12 with Visual FoxPro 9 and MySQL 5.0.41 in
> Traditional Chinese Windows XP pro, tables like below example are
> working fine. Chinese data are displayed normal in VFP aplication and
> Command Line Client, but garbage in MySQL Query Browser.
>
>
> mysql> SHOW CREATE TABLE dsleger\G
> *************************** 1. row ***************************
> Table: dsleger
> Create Table: CREATE TABLE `dsleger` (
> `recnbr` int(10) unsigned NOT NULL auto_increment,
> `no` varchar(12) collate latin1_bin default NULL,
> `code` varchar(12) collate latin1_bin default NULL,
> `acc` varchar(20) collate latin1_bin default NULL,
> `nbr` decimal(8,2) default NULL,
> `price` decimal(9,2) default NULL,
> `i_basic` char(4) collate latin1_bin default NULL,
> `desc` varchar(52) collate latin1_bin default NULL,
> `dc` char(1) collate latin1_bin default NULL,
> `amount` decimal(12,2) default NULL,
> `rmk` varchar(512) collate latin1_bin default NULL,
> PRIMARY KEY (`recnbr`),
> KEY `I_no` (`no`(10)),
> KEY `I_code` (`code`),
> KEY `I_desc` (`desc`)
> ) ENGINE=MyISAM AUTO_INCREMENT=31528 DEFAULT CHARSET=latin1
> COLLATE=latin1_bin COMMENT='DetailSleger'
> 1 row in set (0.00 sec)
>
>
>
> Jerry Schwartz wrote:
> > Did I read somewhere that ODBC 3.x doesn't support UTF-8?
> We're trying to
> > display Chinese characters in MS Access. The characters are
> there in the
> > MySQL data base, and display just fine using our web-based
> applications, but
> > our goal is to allow our users to use MS Access for ad hoc queries.
> >
> > Currently, no matter what I've tried, all I ever see is
> garbage. Will ODBC 5
> > resolve this? Does anyone have any ideas?
> >
> > 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
> >
> >
>
>
> --
> 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: UTF-8

I'm afraid the problem end is in MS Access, if you need to use it, then
may be inevitably you must face it. Long ago in DOS age, these's a
Chinese environment software called Eten, may be your coworker knows it,
since that time Chinese characters are represented by DBCS, mostly BIG5.
I learned from that time - just use binary ASCII code, MS will assemble
them to form proper Chinese characters.

By the way, the reason I use MyODBC 3.51.12 is my VFP9 application was
developed at that time, I compared data type returned by SELECT
carefully between MySQL and VFP9 dbf. When MyODBC evolution to .14 or
..15 or .16 later, I found data type returned is different from .12, and
I'm tired to make other comparison, so just un-installed new version and
re-installed MyODBC 3.51.12 till today. May be your diligent colleague
will find other solutions.


Jerry Schwartz wrote:
> Thanks for the response. It is rather disappointing, because if I understand
> you correctly then MS Access might be the problem.
>
> One of my coworkers is using Chinese XP (I'm not sure if it is traditional
> or not), and I think he has the Chinese version of MS Access. I will have to
> double-check with him, and see if there is anything he can change on his end
> that makes this work.
>
> Do you have any suggestions?
>
> 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: Dennis Yu [mailto:service@dennisyu.idv.tw]
>> Sent: Friday, June 29, 2007 2:04 AM
>> To: Jerry Schwartz
>> Cc: myodbc@lists.mysql.com
>> Subject: Re: UTF-8
>>
>> FYR, I use MyODBC 3.51.12 with Visual FoxPro 9 and MySQL 5.0.41 in
>> Traditional Chinese Windows XP pro, tables like below example are
>> working fine. Chinese data are displayed normal in VFP aplication and
>> Command Line Client, but garbage in MySQL Query Browser.
>>
>>
>> mysql> SHOW CREATE TABLE dsleger\G
>> *************************** 1. row ***************************
>> Table: dsleger
>> Create Table: CREATE TABLE `dsleger` (
>> `recnbr` int(10) unsigned NOT NULL auto_increment,
>> `no` varchar(12) collate latin1_bin default NULL,
>> `code` varchar(12) collate latin1_bin default NULL,
>> `acc` varchar(20) collate latin1_bin default NULL,
>> `nbr` decimal(8,2) default NULL,
>> `price` decimal(9,2) default NULL,
>> `i_basic` char(4) collate latin1_bin default NULL,
>> `desc` varchar(52) collate latin1_bin default NULL,
>> `dc` char(1) collate latin1_bin default NULL,
>> `amount` decimal(12,2) default NULL,
>> `rmk` varchar(512) collate latin1_bin default NULL,
>> PRIMARY KEY (`recnbr`),
>> KEY `I_no` (`no`(10)),
>> KEY `I_code` (`code`),
>> KEY `I_desc` (`desc`)
>> ) ENGINE=MyISAM AUTO_INCREMENT=31528 DEFAULT CHARSET=latin1
>> COLLATE=latin1_bin COMMENT='DetailSleger'
>> 1 row in set (0.00 sec)
>>
>>
>>
>> Jerry Schwartz wrote:
>>> Did I read somewhere that ODBC 3.x doesn't support UTF-8?
>> We're trying to
>>> display Chinese characters in MS Access. The characters are
>> there in the
>>> MySQL data base, and display just fine using our web-based
>> applications, but
>>> our goal is to allow our users to use MS Access for ad hoc queries.
>>>
>>> Currently, no matter what I've tried, all I ever see is
>> garbage. Will ODBC 5
>>> resolve this? Does anyone have any ideas?
>>>
>>> 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
>>>
>>>
>>
>> --
>> 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: UTF-8

This is very frustrating. I just installed version 1.2.12 of the MySQL query
browser, and it displays Chinese characters. It isn't using ODBC, of course.

Are your applications using ODBC? The MySQL command line client doesn't, so
I would expect it to work properly. You said your VFP 9 application is using
ODBC, and it displays Chinese characters, so ODBC is not the problem.

That leaves MS Access.

I'll try looking for MS Access help on the web.

Thanks.

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: Dennis Yu [mailto:service@dennisyu.idv.tw]
> Sent: Friday, June 29, 2007 10:59 AM
> To: Jerry Schwartz
> Cc: 'Jerry Schwartz'; myodbc@lists.mysql.com
> Subject: Re: UTF-8
>
> I'm afraid the problem end is in MS Access, if you need to
> use it, then
> may be inevitably you must face it. Long ago in DOS age, these's a
> Chinese environment software called Eten, may be your
> coworker knows it,
> since that time Chinese characters are represented by DBCS,
> mostly BIG5.
> I learned from that time - just use binary ASCII code, MS
> will assemble
> them to form proper Chinese characters.
>
> By the way, the reason I use MyODBC 3.51.12 is my VFP9 application was
> developed at that time, I compared data type returned by SELECT
> carefully between MySQL and VFP9 dbf. When MyODBC evolution to .14 or
> .15 or .16 later, I found data type returned is different
> from .12, and
> I'm tired to make other comparison, so just un-installed new
> version and
> re-installed MyODBC 3.51.12 till today. May be your diligent
> colleague
> will find other solutions.
>
>
> Jerry Schwartz wrote:
> > Thanks for the response. It is rather disappointing,
> because if I understand
> > you correctly then MS Access might be the problem.
> >
> > One of my coworkers is using Chinese XP (I'm not sure if it
> is traditional
> > or not), and I think he has the Chinese version of MS
> Access. I will have to
> > double-check with him, and see if there is anything he can
> change on his end
> > that makes this work.
> >
> > Do you have any suggestions?
> >
> > 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: Dennis Yu [mailto:service@dennisyu.idv.tw]
> >> Sent: Friday, June 29, 2007 2:04 AM
> >> To: Jerry Schwartz
> >> Cc: myodbc@lists.mysql.com
> >> Subject: Re: UTF-8
> >>
> >> FYR, I use MyODBC 3.51.12 with Visual FoxPro 9 and MySQL 5.0.41 in
> >> Traditional Chinese Windows XP pro, tables like below example are
> >> working fine. Chinese data are displayed normal in VFP
> aplication and
> >> Command Line Client, but garbage in MySQL Query Browser.
> >>
> >>
> >> mysql> SHOW CREATE TABLE dsleger\G
> >> *************************** 1. row ***************************
> >> Table: dsleger
> >> Create Table: CREATE TABLE `dsleger` (
> >> `recnbr` int(10) unsigned NOT NULL auto_increment,
> >> `no` varchar(12) collate latin1_bin default NULL,
> >> `code` varchar(12) collate latin1_bin default NULL,
> >> `acc` varchar(20) collate latin1_bin default NULL,
> >> `nbr` decimal(8,2) default NULL,
> >> `price` decimal(9,2) default NULL,
> >> `i_basic` char(4) collate latin1_bin default NULL,
> >> `desc` varchar(52) collate latin1_bin default NULL,
> >> `dc` char(1) collate latin1_bin default NULL,
> >> `amount` decimal(12,2) default NULL,
> >> `rmk` varchar(512) collate latin1_bin default NULL,
> >> PRIMARY KEY (`recnbr`),
> >> KEY `I_no` (`no`(10)),
> >> KEY `I_code` (`code`),
> >> KEY `I_desc` (`desc`)
> >> ) ENGINE=MyISAM AUTO_INCREMENT=31528 DEFAULT CHARSET=latin1
> >> COLLATE=latin1_bin COMMENT='DetailSleger'
> >> 1 row in set (0.00 sec)
> >>
> >>
> >>
> >> Jerry Schwartz wrote:
> >>> Did I read somewhere that ODBC 3.x doesn't support UTF-8?
> >> We're trying to
> >>> display Chinese characters in MS Access. The characters are
> >> there in the
> >>> MySQL data base, and display just fine using our web-based
> >> applications, but
> >>> our goal is to allow our users to use MS Access for ad
> hoc queries.
> >>>
> >>> Currently, no matter what I've tried, all I ever see is
> >> garbage. Will ODBC 5
> >>> resolve this? Does anyone have any ideas?
> >>>
> >>> 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
> >>>
> >>>
> >>
> >> --
> >> 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: UTF-8

------=_NextPart_000_015D_01C7C93C.D5A32C90
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

Although the 3.51.17 version explicitly allows you to select UTF-8 as the
character set for the connection, I still can't display Chinese characters
in MS Access. As I've mentioned before, MS Access is capable of displaying
Chinese characters if they are copied from a UTF-8 web page and pasted into
Access; so I don't understand what the issue is.

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


------=_NextPart_000_015D_01C7C93C.D5A32C90--