• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Paul Clapham
  • Ron McLeod
Sheriffs:
  • Jeanne Boyarsky
  • Liutauras Vilda
Saloon Keepers:
  • Tim Holloway
  • Carey Brown
  • Roland Mueller
  • Piet Souris
Bartenders:

Production quality JDBC-ODBC driver?

 
Ranch Hand
Posts: 173
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I need to connect to a data source that can only be accessed via ODBC: it's so proprietary that no driver exists for it or its underlying file structure. In addition, the data source is designed such that, to use ODBC, a program must go through a 'client' that forwards the calls to the 'ODBC server.' This client runs only on Windows. I CANNOT rely on the quality of Sun's JDBC-ODBC bridge for this project. Is there a production-quality JDBC-ODBC bridge?
Thanks for your time,
Craig
 
Ranch Hand
Posts: 1879
MySQL Database Suse
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
here is a list from sun:
http://industry.java.sun.com/products/jdbc/drivers/search-results/1,2722,,00.html
You will probably have to pay for them though.
Jamie
 
Craig Demyanovich
Ranch Hand
Posts: 173
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I tried such a search earlier, limiting the results to the JDBC 2.x API. The results were few, but the one thing they had in common was that they each involved a client and a server. The client was really a .jar for the CLASSPATH, like any other JDBC driver. Calls to it would be forwarded to its server, which would translate the calls to ODBC calls, which would then be forwarded on to the data source. We could put the client and the server on the same machine, the server could forward calls to this proprietary driver I mentioned in my last post, and then that driver could forward the calls to the server. I was, however, hoping not to take this "scenic" route; I would rather use a production quality JDBC-ODBC bridge.
Thanks for the response,
Craig
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic