April 10, 2003 at 11:22 am
We've recently updated an old VB app to use trusted connections to a SQL 2000 SP3 server. It connects through to the database fine on developer PCs (with SQL 2000 Client tools installed), however on other PCs we get a SQL Authentication dialog box. If you just accept the default (use trusted connections is ticked already) the user authenticates no problem. Any ideas how we stop this authentication box appearing? I presume that SQL Client tools installs something we need to deploy, but don't know what! Any help much appreciated.
Edited by - ruairidh on 04/10/2003 1:45:16 PM
April 10, 2003 at 11:49 am
Assuming you are using ADO for connection and MDAC is installed on the clients.
Are you using OLEDB connection string?
If so try adding "Integrated Security=SSPI"
If it still comes up, there is way to suppress the connection dialog
ConnectionObject.Properties("Prompt") =adPromptNever
Hope one of this helps
April 10, 2003 at 12:49 pm
We're using the following ODBC connection method:
oConn.Open "Driver={SQL Server};" & _
"Server=MyServerName;" & _
"Database=myDatabaseName;" & _
"Trusted_Connection=yes"
Could this still be a problem with MDAC being out of date on the clients? If so what is the minimum version I should look for to check - 2.6?
April 10, 2003 at 3:25 pm
Good idea to run MDAC 2.6 or higher, and to use OLEDB instead of ODBC. Regardless, the prompt should show up only if you force it, or the connection isn't working. In this case it would seem be to the latter, I'd start by using QA to verify that you can connect to the server as the user.
Andy
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply