Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.0.16, 3.0.3, 3.0.5
-
None
-
Windows 10
Description
I am attempting to use the MariaDB ODBC connector as a replacement for the MyODBC connector and have run into an issue where all DATE and DATETIME fields are being read by the report as having NULL values.
I found the following reference to this issue here: https://apps.support.sap.com/sap/support/knowledge/public/en/2604895
That page describes a workaround (one that would not be practical in my situation) but for the cause says only "MariaDB is not listed in the supported data sources for Crystal Reports". In my case I am using the MariaDB ODBC connector to connect to a MySQL 5.0 database, so something must be different in how the results appear to the report.
I would be happy to provide any additional information in tracking down the difference that is causing the conflict.
Thanks, you've already did more, than I could expect!
That is actually strange, MADB_CopyMadbTimestamp is pretty simple function copying numeric data from one struct(MYSQL_TIME) to another(SQL_TIMESTAMP_STRUCT). And DataPtr you printed is supposed to be the value buffer bound by the application, and it gets value during MADB_CopyMadbTimestamp execution. Since you have debug version, you may want to compare DataPtr value - I mean buffer address it points to, with what is passed to SQLBindCol for the field, to verify those are the same addresses. But that is quite unlikely, that there is error there.
But looking at the crystal report mini trace - it's hard to imagine what causes the error. Pretty basic use of ODBC API.