1 person found this helpful
You'll need to use 32 bit JDK in version 4.0 of SQL Developer
Version 4.1 requires Java 8, which removed the ODBC Bridge feature, which means as a Java application, there's no way for us to 'connect' to an Access 'database'
Thanks Jeff for your prompt reply and information!
Supposedly, newer technology must make our life easier.
There is so much information in MS-Access that I feel like a tool like SQL-Developer in conjuction with APEX, must have a way to migrate Access databases in Oracle.
What is the official answer from Oracle?
What alternatives do you propose?
Removing an essential component, always hurts a lot.
Since it is quite possible and simple to install multiple versions of SQL Developer and Java JDKs, it seems Jeff already gave the official response...
You'll need to use 32 bit JDK (or 64 bit, depending on your MS Access install) in version 4.0 of SQL Developer
The essential component you mention is the ODBC bridge in Java 7 and earlier, which SQL Developer merely took advantage, as it does of so many other features in other Oracle products and even open source projects that Oracle Legal approves for our use. When the ODBC bridge got deprecated from Java we could no longer take advantage of it, except in the past releases.
And, of course, nothing pleases us more than migrating customers to Oracle.
To follow-up, from Compatibility Guide for JDK 8
- Removal of the JDBC-ODBC Bridge
Starting with JDK 8, the JDBC-ODBC Bridge is no longer included with the JDK. The JDBC-ODBC Bridge has always been considered transitional and a non-supported product that was only provided with select JDK bundles and not included with the JRE. Instead, use a JDBC driver provided by the vendor of the database or a commercial JDBC Driver instead of the JDBC-ODBC Bridge.
Interestingly, Microsoft does not provide such a driver (perhaps assuming that others will keep on supporting ODBC?).
Alternatively, this open source project does: UCanAccess-A Pure Java JDBC Driver for Access
However, in order for it to be added as a supported driver in SQL Developer, there would have to be sufficient customer demand and the necessity of logging and pushing an enhancement request.