Re: Windows authentication using Visual Basic to SQL Server 2000

From: Paul Ibison (Paul.Ibison_at_Pygmalion.Com)
Date: 05/27/04

  • Next message: Dinesh T.K: "Re: Unable to load OLEDB provider dll" 
    Date: Thu, 27 May 2004 08:34:51 +0100

    Canaries,

    BTW, the easiest way to create a connection string is to use a UDL file:
    open notepad and save a blank document as xxx.udl. Double click the udl file
    and you'll see the familiar connection wizard. Step through the wizard and
    connect. Next open this udl file in notepad and you'll see the full
    connectionstring. This has to be done on a computer with MDAC (>=2.5 I
    believe).

    Otherwise, here are some examples: (from
    http://www.able-consulting.com/MDAC/ADO/Connection/OLEDB_Providers.htm#OLEDBProviderForSQLServer)
    Trusted: oConn.Open "Provider=sqloledb;" & _
               "Data Source=myServerName;" & _
               "Initial Catalog=myDatabaseName;" & _
               "Integrated Security=SSPI"
    Trusted, local: oConn.Open "Provider=sqloledb;" & _
               "Data Source=(local);" & _
               "Initial Catalog=myDatabaseName;" & _
               "Integrated Security=SSPI"
    Trusted, named instance: oConn.Open "Provider=sqloledb;" & _
               "Data Source=myServerName\myInstanceName;" & _
               "Initial Catalog=myDatabaseName;" & _
               "Integrated Security=SSPI"
    HTH,Paul Ibison

  • Next message: Dinesh T.K: "Re: Unable to load OLEDB provider dll"

    Relevant Pages