Re: SQL Server Driver and Classpath problem
Re: SQL Server Driver and Classpath problem
- Subject: Re: SQL Server Driver and Classpath problem
- From: TW <email@hidden>
- Date: Fri, 5 Sep 2008 07:36:55 -0700
Peter:
That was it. I never would have found that because for SQL Server 2000
I never had to populate a value for "driver" in my connection
dictionary. It always worked just with the url. I don't really
understand why that changed or, better, why the adaptor was looking
for another driver signature but I am just glad it worked and saved my
sanity.
Thanks much for your help!!
Tim
On Sep 4, 2008, at 11:43 PM, Peter Vandoros wrote:
Hi Tim,
If the version of the JDBC driver supports SQL Server 2005, then the
driver class in the eomodel connection dictionary should be
"com.microsoft.sqlserver.jdbc.SQLServerDriver" not
"com.microsoft.jdbc.sqlserver.SQLServerDriver" as the error states
below.
Running a query against the connection gives me this error:
"JDBC connection failed for
driver :'com.microsoft.jdbc.sqlserver.SQLServerDriver'. Driver not
found in Java Runtime!"
Regards
Peter Vandoros
Software Engineer
Etech Group Pty Ltd
Level 3/21 Victoria St
Melbourne VIC 3000
Australia
Ph: +61 3 9639 9677
Fax: +61 3 9639 9577
----------------------------------
IMPORTANT: This e-mail message and any attachments are confidential
and may be privileged. If received in error, please reply to this
message and destroy all copies and any attachments. You should check
this message and any attachments for viruses or defects. Our
liability is limited to resupplying any affected message or
attachments. For more information about Etech Group, please visit us
at http://www.etechgroup.com.au.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden