windows 10

I've tried it in MsAccess linking to a DSN using ODBC and it also gives an error

insert into TestDB.TestTable (FieldDate) values (cdate("12-12-1910"))

Using 'Mysql Odbc' driver or HeidiSql works fine.

It seems MariaDb processes datatime fields as timestamp fields, which only are allowed values between 1970 and 2038

Thank you for your report. I assume your script still produces error, and does not crash the application.

What server version do you use?
In your create statement in the script, field's type is the datetime, not the timestamp. Is the type of field in your table really datetime or timestamp? Since you say that with mysql's driver and HeidiSql these dates work, I'd imagine it's the datetime.

What is TestDB.TestTable in your comment about test in MsAccess?

the server version is 10.6.5

I use always datetime fields, but I've read data problem occurs in timestamp fields.
In mysql drivers works fine, but in MariaDb drivers fails.
I never use MsAccess, the previous comment is only to test purpose.
All the lines of my script works fine, but the line that assigns fecha to 0 crashes

I've read too MariaDb CONNECTOR fails on write dates not between 1970 and 2038
It seems the connector handles datetime fields as timestamp fields.

The server version or the client used does not matter, fails on all the versions.
Only the odbc driver is affected.

The table is the following:

CREATE TABLE `testtable` (`FieldDate` DATETIME NOT NULL DEFAULT '1899-12-30 00:00:00')
COLLATE='utf8_general_ci' ENGINE=InnoDB ;

You can see the error inserting data on the following PrintScreen (https://www.levelprograms.com/descargas/Error%20Insert%20date%20MariaDB%20Odbc.png)

Thanks

Thanks for your interest and your fast reply.
Do you know when 3.1.15 version will be avaiable to download?

If nothing goes wrong - it will be released this week