I have done a net search on this topic and none of what I have found seems to apply to my case. I am in the middle of changing an existing application from JDBC-ODBC Bridge to UcanAccess. The error/warning occurs when I try to execute SQL. The table I am going against does not have a binary key. There are no binary fields in the table. The PK is a multi-column text key, based on meaningful field values.
Can you advise me how to eliminate this message? This is not mission-critical since the SQL executes regardless. I just have an inborn programmer's drive to write code that does not issue warnings or errors. Thank you for your help.
Dave Martin
Last edit: David Martin 2015-03-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Firstly I would try to use the ms access compact and repair tool.
Should the message be logged despite of, I would ask for help to the jackcess team, you know, it's a jackcess message. So if you tried to open your db with jackcess directly, the message would appear as well.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have done a net search on this topic and none of what I have found seems to apply to my case. I am in the middle of changing an existing application from JDBC-ODBC Bridge to UcanAccess. The error/warning occurs when I try to execute SQL. The table I am going against does not have a binary key. There are no binary fields in the table. The PK is a multi-column text key, based on meaningful field values.
Can you advise me how to eliminate this message? This is not mission-critical since the SQL executes regardless. I just have an inborn programmer's drive to write code that does not issue warnings or errors. Thank you for your help.
Dave Martin
Last edit: David Martin 2015-03-04
Firstly I would try to use the ms access compact and repair tool.
Should the message be logged despite of, I would ask for help to the jackcess team, you know, it's a jackcess message. So if you tried to open your db with jackcess directly, the message would appear as well.
All right. Thank you.
I don't see any place where Jackcess offers support. Do you have suggestions?
Thank you.
Yes, of course, here:
https://sourceforge.net/p/jackcess/discussion/?source=navbar
Cheers Marco
This may well be fixed in the next version of Jackcess (2.0.9). Revision 921 of the Jackcess source code appears to address the issue:
"Implement support for indexes on BINARY fields"
If so, then the problem should go away for UCanAccess once UCanAccess starts using Jackcess 2.0.9.