|
From: Robert M. <rob...@gm...> - 2006-03-12 10:50:58
|
On 3/12/06, Matthew Dahlman <mda...@su...> wrote: > > The first step you should try is to run squirrel-sql.bat from the command > line as the previous email suggests. This is generally the easiest way to > find out what's wrong. > > In your case it sounds like SQuirreL isn't finding java. Your technique o= f > solving it was "move Java to SQuirrel". I think you'll find it's better t= o > try the technique of "point SQuirreL to Java". To do this you could modif= y > environment variables so that JAVA_HOME is well defined. But I find it > easier to directly modify squirrel-sql.bat so I know exactly what's going > on. > Careful with this approach. It becomes a maintenance headache each time yo= u want to upgrade to the next version. If we make changes to the distributed version of squirrel-sql.bat, then you have to merge your local changes in each time you upgrade. > You probably have a JRE rather than a JDK (or SDK or whatever it's > called). So your path to it will be something like this: C:\Program > Files\Java\jdk1.5.0_06\bin\java > Don't forget to put quotes around the path if you are using the JRE: SET LOCAL_JAVA=3DC:\Program Files\Java\jdk1.5.0_06\bin\java should be: SET LOCAL_JAVA=3D"C:\Program Files\Java\jdk1.5.0_06\bin\java" Rob |
