Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Incomplete
-
3.1.16
-
None
-
Access frontend. MariaDb backend. Linked using DSN-less connections (but also happens if using regular DSN).
64b Access 16.0.15427.20194, Windows 11 (also happens Windows 10)
Problem occurs on:
Maria ODBC connector 3.1.16, Maria Server 10.3.22
Maria ODBC connector 3.1.16, Maria Server 10.8.3
Problem does NOT occur on:
Maria ODBC connector 3.0.8, Maria Server 10.3.22
Connection string:
DRIVER={MariaDB ODBC 3.1 Driver};SERVER=localhost;PORT=3306;DATABASE=ctu;USER=root;OPTION=67108914;Trusted_Connection=Yes;
Access frontend. MariaDb backend. Linked using DSN-less connections (but also happens if using regular DSN). 64b Access 16.0.15427.20194, Windows 11 (also happens Windows 10) Problem occurs on: Maria ODBC connector 3.1.16, Maria Server 10.3.22 Maria ODBC connector 3.1.16, Maria Server 10.8.3 Problem does NOT occur on: Maria ODBC connector 3.0.8, Maria Server 10.3.22 Connection string: DRIVER={MariaDB ODBC 3.1 Driver};SERVER=localhost;PORT=3306;DATABASE=ctu;USER=root;OPTION=67108914;Trusted_Connection=Yes;
Description
After linking tables from MariaDb Access shows absolutely no primary keys ... for any table ... even if the only key is an autonumber. Although this seems likely related to the recent varchar PK reports ... this is all of them.
The old driver still seems to work with the latest Access client. Although last year I had to rewrite the connection strings to use OPTION instead of the parameter names (Access seems to have stopped connecting based on parameter names and only the OPTION value).
Attachments
Issue Links
- is caused by
-
-
- Closed
-