Cetin,
I get the following error message when I use a Connection String as you had specified and I don't know what it really means even though I read Microsoft Knowledgebase articles on it.
Failed to open the connection.
Followed by this error message when I click OK.
IM006:[Microsoft][ODBC Driver Manager]Driver's SQLSetConnectAttr failed[Database Vendor Code: 17]
Followed by this error message when I click OK
Failed to open the connection.
Details: 01000:[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect()). [Database Vendor Code: 17]
Followed by this error message when I click OK
Similar to above message but Details: 08001: [Microsoft][... ... ... Server does not exist or access denied... ...
And I checked the Connection to the VPN and it is working fine and I am connected to the SQL Server from my remote location.
I researched this error-problem using the Microsoft Knowledgebase, but after reviewing several different articles, I am not sure what my problem is, but I think it has to do with one of the following:
• Microsoft ODBC Driver for Microsoft SQL Server 3.6
• Microsoft SQL Server 2000 Standard Edition
• Microsoft Data Access Components 2.6
I will keep researching and studying the problem.
I tired the trusted connection and the User ID/Password method also. I'm with you, I prefer the trusted_connection method. But so far nothing is working.
I don't think I need SQL Server on my machine if I use a Connection String? But do I need an SQL Driver on my machine or MDAC on my machine? Something seems to be missing somewhere and I don't know what and I don't know where.
Thanks for your help. I really appreciate it. I'm sure I can get this thing working soon.
Steve Kramer
Kramer & Kramer Design
"Home of Go Cartoons"
Web Site:
www.stephenkramer.comWould you believe Far Side Lite?
More than 270 original cartoons.