Emmanuel, Thanks for your reply. I have tried using derby.jar instead of derbyclient.jar and the result is exactly the same. Is there any more advice you can give me?
Thanks, Mike Emmanuel Cecchet-5 wrote: > > Michael, > > You should have derby.jar in the classpath if you want to use embedded > mode. >> CLASSPATH=\ >> Applications/apache-tomcat-6.0.18/lib/derbyclient.jar:\ > derbyclient.jar contains only the JDBC driver code > (http://db.apache.org/derby/docs/dev/adminguide/tadminappschangingyourclasspath.html) >> <% >> String driver = "org.apache.derby.jdbc.EmbeddedDriver"; > > Hope this helps, > Emmanuel > > -- > Emmanuel Cecchet > FTO @ Frog Thinker > Open Source Development & Consulting > -- > Web: http://www.frogthinker.org > email: [EMAIL PROTECTED] > Skype: emmanuel_cecchet > > > -- View this message in context: http://www.nabble.com/Tomcat-derby-JSP-%22java.sql.SQLException%3A-No-suitable-driver%22-tp20776666p20840073.html Sent from the Apache Derby Users mailing list archive at Nabble.com.
