Re: Connecting using Windows Authentication

You would use the following to authenticate using Windows NT integrated
security:

Set cnDB = CreateObject("ADODB.Connection")
cnDB.ConnectionString = "Provider=SQLOLEDB.1;Integrated Security=SSPI;" _
& "Persist Security Info=False;Initial Catalog=ProjectServer;Data
Source=jnicapproject"

HTH,
Branden Johnson

"Shane" <Shane@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D9E36D21-C3A9-4C1B-988E-7676684DA35D@xxxxxxxxxxxxxxxx
> Dirk - the connection string looks like this:
>
> Set cnDB = CreateObject("ADODB.Connection")
> cnDB.ConnectionString = "Provider=SQLOLEDB.1;" _
> & "Initial Catalog=ProjectServer;Data Source=jnicapproject"
>
> As you can see, I've left off the userid and password parameters. When I
run
> it, I get an "Invalid Authorization Specification" error. I'm assuming
that
> the SQL Server provider is expecting something to let it know how to log
in
> the user.
>
> "Dirk" wrote:
>
> > As far as I know, and I must admit I have very limited knowledge
regarding
> > this issue, you do not have to enter anything at all providing that the
user
> > context the access.exe process runs under has appropriate rights on the
sql
> > database you are trying to approach.
> >
> > "Shane" wrote:
> >
> > > When connecting to SQL Server from Access, how does one connect using
Windows
> > > Authentication rather than a login name and password? Is it possible
or do I
> > > need to have the Admin give me an account?
> > > Thx,
> > > Shane


.

Relevant Pages

  • Re: Why do I have to enable File and Printer sharing to connect through the XP firewall?
    ... the connection string. ... IS the client connecting using a Windows account or using a SQL Server account? ... the user is me and I'm a domain/olap admin. ...
    (microsoft.public.sqlserver.clients)
  • Re: SQL open error
    ... I wish to use Windows authentication rather than supplying ... in Enterprise Manager reads as. ... Source=localhost in my connection string I get the error ... "SQL server does not exist or access denied". ...
    (microsoft.public.dotnet.general)
  • Deployment issue - Error 26
    ... The target environment is a dedicated server running SQL Server 2005 Standard ... and client machines running the VS2005-developed code on Windows XP. ... testing looked OK after changing the connection string in the app config file. ... It built a connection string and stored it in the Project settings for the data ...
    (microsoft.public.dotnet.framework.adonet)
  • SQL Server does not exists... Yada, yada, yada
    ... Machine running ASP.Net is either a Window 2000 Pro or Windows XP Pro ... running SQL Server 2000. ... The DLL knows how to find it's own connection string from ... domain users account, and whilst running under the local system ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Login failed for user (null)
    ... If using kerberos to authenticate, you may need to enable kerberos ... Server connection. ... EM sits on a developer's PC running XP Professional SP2, and SQL Server ... Standard Ed. SP4 resides on a Windows 2000 Server ...
    (microsoft.public.sqlserver.security)