Why isn't the Easysoft JOB implemented as a Type 4 driver?

Easysoft JDBC-ODBC Bridge

Why isn't the Easysoft JOB implemented as a Type 4 driver?

Article :	00414
Last Reviewed :	19th July 2005
Revision :	1

It is true that type 4 drivers use machine resources more efficiently than type 3 drivers, as there is no middleware server. However, a type 4 driver is specific to the database engine. If a new database management system arrives then the type 4 driver needs to be scrapped or re-written. With the Easysoft JOB you only need to install an ODBC driver for the new DBMS and no other changes need to be made. In addition, a type 3 driver provides both ends of the network connection, allowing connection to database engines that do not normally provide networked access.

Applies To

Products
- Easysoft JDBC-ODBC Bridge

*	Did this content help you? Yes No Maybe

*	Please select one option based on your first choice: I'm very satisfied I think it will help, but I haven't tried it yet It is helpful, but I need more information It is helpful, but hard to understand Seemed relevant in search results, but didn't help me The information is incorrect The page contains one or more broken links

	Suggest new content or let us know how we can improve this content:

	(* Required Fields)

Easysoft JDBC-ODBC Bridge

Why isn't the Easysoft JOB implemented as a Type 4 driver?

Applies To

Knowledge Base Feedback