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