Thread: Missing drivers?

I'm a little confused. The fololwing code compiles without error:

import java.net.*;
import java.sql.*;
import java.io.*;
import java.util.*;
 
class MakeDB
{
     public static void main (String args[])
     {
          try
          {
               Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); // force loading of driver
               String url = "jdbc:odbc:BIBLIO";
               String user = "";
               String password = "";
               Connection con = DriverManager.getConnection(url,user,password);
               Statement stmt = con.createStatement();
               ResultSet r=stmt.executeQuery("SELECT TITLE,AUTHOR FROM TITLES, AUTHORS WHERE TITLES.AU_ID=AUTHORS.AU_ID AND AUTHORS.AU_ID<10");
               while(r.next())
               {
                    String s1=r.getString("title");
                    String s2=r.getString("AUTHOR");
                    System.out.println(s1+ " "+s2);
               }
               stmt.close();
               con.close();
         }
         catch (Exception ex)
         {
              System.out.println ("Exception "+ex);
         }
     }
}

However, when I try to run it throws an exception:

Exception java.lang.ClassNotFoundException: jdbc.odbc.JdbcOdbcDriver

And when I replace jdbc.odbc.JdbcOdbcDriver with a driver I know I have, such as Sun.JavaDB.javadoc.jdbc3.org.apache.derby.jdbc.Emb eddedDriver, it throws this exception:

Exception java.lang.ClassNotFoundException: Sun.JavaDB.javadoc.jdbc3.org.apache.derby.jdbc.EmbeddedDriver

.

Am I missing something basic about the packages that the JDBC drivers?

Are the driver packages on your classpath? If not, you need to add them to the classpath (eg let the jvm know where the packages are), which is typically IDE dependent.

I'm just using Notepad and the command line.

I'm not sure how to add packages to my classpatth.

Setting the class path

Can I have it included in the standard package by moving the directory where the standard packages are located?

Try it and see. If I understand you correctly and you mean to add it where the standard jdk jar's reside, if your app is a distributed one, you usually want the jar's explicitely associated with the project since doing so make it easier to 'run anywhere'. IDE's make doing this a lot easier, where you add a jar to a project and the classpath is immediately set and the jar's can be packaged and distributed together