I am not a Java developer. I am just trying to configure an application's (http://birst.com) integration to an Access accdb file using UCanAccess. We had previously been using pure ODBC but having had to upgrade to Java 8, that is no longer an option.
You're right, the character $ in a table/column name seems to be problematic for hsqldb, and this has never been reported before. Hope to be able to fix it in the 3.0.3.Our aim is to support each column/table name a human mind can generate regardless the alphabet used. I thought this was already achieved, but it isn't.
Last edit: Marco Amadei 2015-11-16
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am not a Java developer. I am just trying to configure an application's (http://birst.com) integration to an Access accdb file using UCanAccess. We had previously been using pure ODBC but having had to upgrade to Java 8, that is no longer an option.
The conection string I am using is...
jdbc:ucanaccess://Z:\Revenue\Revenue Database\012312_Revenue Database.accdb;lockmdb=false;memory=false
In the resulting log file I see the following line...
2015-11-16 10:21:41 PST DEBUG Finished reading system catalog. Tables: [CUSTOMER VERTICAL, Load$_ImportErrors, Name AutoCorrect Save Failures, Parent, Product Code Lookup, Product Lookup, ProductHierarchy, Q2 Revenue Data, REVENUE DATA, UniqueProductNameTable] (Db=012312_Revenue Database.accdb)
Which leads me to believe that the driver did make a connection to the Access db as it could actually read the table names.
But the interface fails shortly after this message with the following error...
2015-11-16 10:21:41 PST ERROR Connection to the JDBC driver failed: net.ucanaccess.jdbc.UcanaccessDriver, UCAExc:::3.0.0 unexpected token: LOAD$_IMPORTERRORS, unexpected token: LOAD$_IMPORTERRORS
The query it is intended to execute, but never gets to, is SELECT * FROM Parent;
I should say that for another Access db the interface is working perfectly well.
Thanks in advance for any direction/insight you can provide.
You're right, the character $ in a table/column name seems to be problematic for hsqldb, and this has never been reported before. Hope to be able to fix it in the 3.0.3.Our aim is to support each column/table name a human mind can generate regardless the alphabet used. I thought this was already achieved, but it isn't.
Last edit: Marco Amadei 2015-11-16
Fixed in svn trunk.