>>
Thanks, tried it but it didn't work. Any other ideas?
<<
Well looking in some old code I noticed this was how I got the driver
"registered":
>>
// Do it both ways for kicks:
Class clsDriver = Class.forName( "package.SomeDriverName" );
DriverManager.regist
>>
Connection: java.sql.SQLException: No suitable driver message. At first
I
though it was CLASSPATH problem, but I returned the CLASSPATH along with
the error message and the jar file for the jdbc driver is listed.
<<
Total long shot here, but I just noticed on one of our servers I
unzipped th
