Windows authentication using Visual Basic to SQL Server 2000

From: canaries (anonymous_at_discussions.microsoft.com)
Date: 05/26/04 

Date: Wed, 26 May 2004 13:31:06 -0700

I have a program in Visual Basic, and I want to connect to SQL Server using Windows Authentication. I have no problems using my SQL login using the following connect string:

Provider=sqloledb;Persist Security Info=False; Data Source=TWCDEV1.twcglobal.com; initial catalog=Wnrc; User ID=Wnrcadmin; password=????;

Any help on the connection string using Windows authentication?

Relevant Pages

  • Re: Cannot connect using sa
    ... > Make sure you have it configured to allow both SQL Server ... > Windows authentication only. ... I removed the password and user from the connection string. ... >>Login failed for user 'sa'. ...
    (microsoft.public.sqlserver.setup)
  • Re: sysprocesses and Visual Basic Program
    ... I did see that I could use windows authentication. ... > current user is logged in to SQL Server using SQL Server Authentication, ... > SYSTEM_USER returns the SQL Server login identification name, for example, ... use windows authentication in your connection string. ...
    (microsoft.public.sqlserver.programming)
  • Re: Unable to get SQLConnection to Open() in BackgroundWorker
    ... Have you tried posting your question in the SQL Server Security forum? ... The connection string used with Windows authentication must include either the ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Cant Connect
    ... password in the connection string. ... You can find sample connection strings using the SQL Server ... Sql server set to use Windows Authentication ... > dim Cn, CnStr ...
    (microsoft.public.sqlserver.connect)
  • Re: Newbie Cant connect - Trusted Server issue.
    ... You also might want to verify the connection string you are using is ... >> I'm creating an application that will rely on a central SQL Server ... > With Windows authentication, SQL Server accepts your Windows user, ... > username and password that SQL Server itself validates. ...
    (microsoft.public.sqlserver.connect)
Loading