The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-15. For the latest, interactive version please visit https://mariadb.com/kb/.

Problem Connector ODBC between MariaDB and ACCESS

Hello, I have a problem with the connection between ACCESS (2010), running with W7, and a MariaDB installed on a Synology NAS (DS212J). Test of DSN is OK. Import and link tables from NAS towards ACCESS are OK. But export from ACCESS is impossible: alert message says: " "ODBC l'appel a échoué (the call failed) [ma-2.0.10][5.5.49-MariaDB]You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '#O),'C_UFR' INTEGER('#O),'U_SECRETARIAT' VARCHAR,'U-2SECRETARIAT' VAR at line 1 (#1064)" I thank you

Complementary Infos: The pb is the same with 1.0.6 2.0.10 2.0.11 releases of mariadb connector (32 and 64 bits) C_UFR, U_SECRETARIAT ant U_2SECRETARIAT are the three first fields of the table i try to export. Setting of the NAS: • Serveur : Localhost via UNIX socket • Type de serveur : MariaDB • Version du serveur : 5.5.49-MariaDB - Source distribution • Version du protocole : 10 • Jeu de caractères du serveur : UTF-8 Unicode (utf8) Serveur Web: • nginx/1.9.11 • Version du client de base de données : libmysql - mysqlnd 5.0.11-dev - 20120503 - $Id: 76b08b24596e12d4553bd41fc93cccd5bac2fe7a $ • Extension PHP : mysqli curl mbstring • Version de PHP : 5.6.21

Answer Answered by jlpierrey_52563 in this comment.

Hi all, I solve the problem: i use the MySQL ODBC connector (see https://dev.mysql.com/downloads/connector/odbc/) and the exchanges between MS ACCESS and the Mariadb db of my Synology NAS work perfectly. A bug in the MariaDB connector (release 2.0.12 included) is probably the cause of its misfunction in this case.

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.