A. Rick Anderson wrote:
I'm getting a "driver not found" exception when running a relatively
trivial derby program from within eclipse. It's frustrating because I
can crack the derby.jar file and the targeted driver class is in the
derby.jar file that is in the build path for the project.
...
private static final String derbyClientDriver =
"org.apache.derby.jdbc.ClientDriver";
The client driver is usually in derbyclient.jar, not in derby.jar.
It's the *embedded* driver that is in derby.jar.
Could that be the problem?
thanks,
bryan
