Knut Anders Hatlen wrote:
You shouldn't load the client driver unless your application uses jdbc:derby://localhost/mydb. The reason why the client driver seems to work in your case, is that the server already has loaded the embedded driver. So the code that runs inside the same JVM as the server should use jdbc:derby:mydb and not load the client driver, whereas the external scripts should load the client driver and use jdbc:derby://localhost/mydb.
That makes sense :-) Thanks for all your help! -- Alan Burlison --
