Hello again, Tim!
Yeah, I have no clue why JBuilder decided to pull in 3.1.12. I found a way to cut it from the classpath, although I still can't figure out how to change the order of the classpath so 3.1.8 comes before myprogram.
Good news, moving the 3.1.8 jar out of Code and into jre.lib has stopped it from getting the "NoClassDefFound" run-time error for Driver.class. (Only shows up when a database is specified.) Unfortunately, the other problems,
are still bouncing back when I try to get it into a database.
I'm going to poke around with directory structure a bit more to see if there's another (unusable) version of MySQLDriver that's being loaded when myprogram is loaded first.
Thanks for the brains,
Zachary
Originally posted by Tim LeMaster:
Well at first glance I see 3 versions of the mysql jar. I would get all but one of them out of the build path and out of the class path. Apparently mysql-connector-java-3.1.8-bin.jar was the one that worked, I'd stick with it.
I would get mysql-connector-java-3.1.8-bin.jar out of the src directory as thats probably confusing things even more. I'd create a lib directory and put all third party required jars in there.
From there you can either list the jars in your Class-Path of the manifest file as lib/thejar.jar and use java -jar to start the program or you can create a batch file very much like the one you describe and launch your program with the classname.
Good luck!