>>
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
On Thu, 7 Jan 1999, Ben Newman wrote:
> Thanks, tried it but it didn't work. Any other ideas?
Have you tried registering the jdbc driver yourself, rather than relying
on the driver doing it itself?
In the early days of the PostgreSQL driver, we had a similar problem. When
we found that registe
Thanks, tried it but it didn't work. Any other ideas?
On Wed, 6 Jan 1999, Scott Fraser wrote:
> >>
> 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 fo
On Wed, 6 Jan 1999, Ben Newman wrote:
> I'm having a problem with servlets that use JDBC. I have a servlet that
> runs a simple query and returns some rows. As a stand alone app it works
> just fine, but when I switch it over to run as a servlet I get a Error
> Connection: java.sql.SQLException
>>
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
