PRB: No Suitable Driver Exception With JDBC Bridge and SDKLast reviewed: January 29, 1998Article ID: Q179854 |
The information in this article applies to:
SYMPTOMSWhen running your Java class that uses the JDBC bridge with the SDK for Java 2.0 or newer, you see the following exception:
java.sql.SQLException: No suitable driver CAUSEOne of the frequent causes for this exception is running any application that the JDBC bridge shipped with the SDK for Java 2.0 Beta.
RESOLUTIONIn general, the package name has changed to com.ms.jdbc.odbc with Internet Explorer 4.0x and SDK for Java 2.0x Virtual Machines. For example the following lines should be changed:
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); -or- Class.forName("com.ms.sql.CDriver");to:
Class.forName("com.ms.jdbc.odbc.JdbcOdbcDriver"); MORE INFORMATIONOther common causes for "No suitable driver" are invalid connection strings, user IDs, passwords, and security restrictions imposed on the driver (if it was downloaded and is not trusted).
REFERENCESMore information on the JDBC driver is included the SDK 2.0x for Java documentation and the "JDBC" sample available with the SDK2.0x. For the latest Knowledge Base articles and other support information on Visual J++ and the SDK for Java, see the following page on the Microsoft Technical Support site:
http://support.microsoft.com/support/visualj/ http://support.microsoft.com/support/java/ Keywords : JDB Technology : kbInetDev internet odbc Version : WINDOWS:2.0,2.01 Platform : WINDOWS Issue type : kbprb |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |