MySQL Bugs: #42038: MS ACCESS problems with UTF-8 PRIMARY KEY

Bug #42038	MS ACCESS problems with UTF-8 PRIMARY KEY
Submitted:	12 Jan 2009 2:45	Modified:	8 Dec 2010 9:31
Reporter:	Mike Mosiewicz	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	5.01.05.00	OS:	Windows (XP/Vista)
Assigned to:	Lawrenty Novitsky	CPU Architecture:	Any
Tags:	#DELETED, MSAccess

Description:
I've got the following table:

CREATE TABLE  `Waluty` (
  `Waluta` char(3) NOT NULL default '',
  `Kurs` double default '0',
  `Zaokraglenie` smallint(6) default '0',
  `x` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
  PRIMARY KEY  (`Waluta`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

The table contains utf8 data. The 'Waluta' field contains three letter currency codes. If the PRIMARY KEY contains any character beyond ASCII - for example polish letter 'Ł' - it appears as #DELETED in access (not after update, but also in queries).

I tried different settings like BIGINTs, dont's use setlocale, safe options - with no luck.

How to repeat:
CREATE TABLE  `Waluty` (
  `Waluta` char(3) NOT NULL default '',
  `Kurs` double default '0',
  `Zaokraglenie` smallint(6) default '0',
  `x` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
  PRIMARY KEY  (`Waluta`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;
INSERT INTO `Waluty`( `Waluta`) VALUES ( 'SZŁ' );

Then open the table linked in ms access. You'll see #DELETED instead.

Verified as described. Not sure what to do about it yet.

I have the same problem, for the moment I can not find solution

Strange, it fails only if type non-latin symbols.
MS Access shows the content if replace "SZŁ" with "ABC".

I have been able to repeat the problem when linked MS SQL Server tables with NCHAR(3) column as Primary Key. This confirms the fact of the actual problem in MS Access.

Setting the status "Not a bug".

Hi,

Couldn't anyone solved this problem?