This configuration requires every client that will run the application to have the JDBC-ODBC bridge API, the ODBC driver and the native language-level APIs. As a result this kind of driver is most appropriate on a corporate network where client installations are not a major problem. Jdbc database calls are translated into vendor-specific API calls. The database will process the request & send the result back through the API, which in turn forwards them back to the Jdbc drivers for Farmville Mystery Eggs Trick. The Jdbc driver translates the result to the Jdbc standard & returns them to the Java application, hence this kind of driver has same problem that was with Jdbc-Odbc driver and is mostly used in Intranet.

Share and Enjoy:
  • Print
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Blogplay