MySQL Bugs: #110274: Foreign characters in primary key show #Deleted in MS Access table through ODBC

Bug #110274	Foreign characters in primary key show #Deleted in MS Access table through ODBC
Submitted:	6 Mar 2023 4:26	Modified:	6 Mar 2023 12:13
Reporter:	Masashi Fukuda	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	ODBC 8.0.32	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	#DELETED, Access 2016, ANSI Driver, foreign characters, MySQL 8.0, ODBC Connector, primary key, Special Characters, Unicode Driver

Description:
I create a table, and insert data, primary key contains foreign character.(Japanese)

Looking at the linked table in Access 2016 through ODBC 8.0.32(Unicode driver), record1 looks like no problems, but record2(primary key containing foreign characters) displayed #Deleted.

#Deleted #Deleted #Deleted
*Export from Access, convert to local table, and report looks like no problems.

Otherwise, through ODBC 8.0.32(ANSI driver), looks like no problems.
But data contains character of out of range ANSI character(ex.𠮷), failed to call odbc driver, and displayed #Name?.
record3:key1=1,key2="c",val1="𠮷"

record1: #Name? #Name? #Name?
record2: #Name? #Name? #Name?
record3: #Name? #Name? #Name?

Best regards,

How to repeat:
1) Create New Table
CREATE TABLE `pk_test` (
  `key1` int NOT NULL,
  `key2` varchar(10) COLLATE utf8mb4_bin NOT NULL,
  `val1` varchar(10) COLLATE utf8mb4_bin DEFAULT NULL,
  PRIMARY KEY (`key1`,`key2`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin;

2) Insert dada
insert into pk_test set (1, "a", "あ");
insert into pk_test set (2, "あ", "あ");

3) Open MS Accesss, create linked table to 'pk_test', and open it.

Then #Deleted displayed.

Version info change

I forgot to write it down.

1) Create database options.
ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_bin 

2) ODBC Configuration.
At MySQL Connector/ODBC Data Source Configuration, Character Set set to utf8mb4.

Hello Masashi Fukuda,

Thank you for the bug report.
Imho this is duplicate of Bug #70297, please see Bug #70297.

Regards,
Ashwini Patil