sqloledb Provider and dbmssocn

Ask a Question related to ASP Database, Design and Development.

  1. #1

    Default Re: sqloledb Provider and dbmssocn

    :-) Whichever one works?

    Seriously, I've alway used the first version: Network Library=DBMSSOCN

    Bob Barrows

    Luis wrote:
    > I've listed two slightly different connection strings below. Which one
    > is the correct one?
    >
    > Should I be using:
    >
    > Network Library=DBMSSOCN
    > or
    > Network=DBMSSOCN
    >
    >
    > The connection strings are:
    >
    > <%
    > dim conn
    > cst = "Provider=SQLOLEDB;Server=myServerName;Database=my DatabaseName;"
    > cst = cst & "Network Library=DBMSSOCN;uid=myUsername;pwd=myPassword"
    > set conn = Server.CreateObject("ADODB.Connection")
    > conn.open cst
    > %>
    >
    > and
    >
    > <%
    > dim conn
    > cst = "Provider=SQLOLEDB;Server=myServerName;Database=my DatabaseName;"
    > cst = cst & "Network=DBMSSOCN;uid=myUsername;pwd=myPasswor d"
    > set conn = Server.CreateObject("ADODB.Connection")
    > conn.open cst
    > %>
    >
    >
    > Thanks


    Bob Barrows Guest

  2. Similar Questions and Discussions

    1. xml into a data provider
      I have constructed a xml file out of php you can find it here: http://dinogod.adrianhosting.com/smf/coverflow/list.php I need to be able to load...
    2. ASP.NET and OLE DB Provider problems
      Hi All, I have problem to accessing FoxPro database, located on Novell file server, over the VFPOLEDB.1 provider from my webservice. The...
    3. Provider error?
      What is GetConnectionString? A function? Where is it? What does it say? Ray at work "Dean J. Garrett" <deanj_garrett@yahoo.com> wrote in...
    4. ASP.NET Hosting Provider
      www.crystaltech.com I just started using them and they are great so far! What I look for is tech support response time and customer care. the price...
    5. Looking for a free ASP.NET provider
      It needs to support code behind. Would be great if it allows publishing from VS.NET, but if not, at least have FTP. Thanks.
  3. #2

    Default Re: sqloledb Provider and dbmssocn

    I've always used just Network. (See [url]http://www.aspfaq.com/2126[/url] and
    [url]http://www.aspfaq.com/2082[/url])


    "Luis" <andyza@webmail.co.za> wrote in message
    news:69476b6f.0308070227.6e1be385@posting.google.c om...
    > I've listed two slightly different connection strings below. Which one
    > is the correct one?
    >
    > Should I be using:
    >
    > Network Library=DBMSSOCN
    > or
    > Network=DBMSSOCN
    >
    >
    > The connection strings are:
    >
    > <%
    > dim conn
    > cst = "Provider=SQLOLEDB;Server=myServerName;Database=my DatabaseName;"
    > cst = cst & "Network Library=DBMSSOCN;uid=myUsername;pwd=myPassword"
    > set conn = Server.CreateObject("ADODB.Connection")
    > conn.open cst
    > %>
    >
    > and
    >
    > <%
    > dim conn
    > cst = "Provider=SQLOLEDB;Server=myServerName;Database=my DatabaseName;"
    > cst = cst & "Network=DBMSSOCN;uid=myUsername;pwd=myPasswor d"
    > set conn = Server.CreateObject("ADODB.Connection")
    > conn.open cst
    > %>
    >
    >
    > Thanks

    Aaron Bertrand - MVP Guest

  4. #3

    Default Re: sqloledb Provider and dbmssocn

    "Aaron Bertrand - MVP" <aaron@TRASHaspfaq.com> wrote in message news:<eSbM8yOXDHA.1900@TK2MSFTNGP10.phx.gbl>...
    > I've always used just Network. (See [url]http://www.aspfaq.com/2126[/url] and
    > [url]http://www.aspfaq.com/2082[/url])
    >
    Thanks.

    Is there a particular reason why there is an "Important note" on the
    "How to define which network protocol to use" / "Read More" section of
    the "SQL Server" entry on [url]www.connectionstrings.com[/url] that says:

    When connecting through the SQLOLEDB provider use the syntax
    Network Library=dbmssocn
    and when connecting through MSDASQL provider use the syntax
    Network=dbmssocn
    Luis Guest

  5. #4

    Default Re: sqloledb Provider and dbmssocn

    Luis wrote:
    >
    > Is there a particular reason why there is an "Important note" on the
    > "How to define which network protocol to use" / "Read More" section of
    > the "SQL Server" entry on [url]www.connectionstrings.com[/url] that says:
    >
    > When connecting through the SQLOLEDB provider use the syntax
    > Network Library=dbmssocn
    > and when connecting through MSDASQL provider use the syntax
    > Network=dbmssocn
    The MSDASQL provider is also known as the "Microsoft OLEDB Provider for
    ODBC". ODBC is the older database communication technology that has been
    superseded by OLEDB. The ODBC interface has different names for all of these
    attributes than the OLEDB interface. Notice when using MSDASQL, that you use
    UID for the user name, while the native OLEDB provider uses User ID, etc.

    Microsoft recommends using native OLEDB providers when available for the
    database you are using, avoiding the MSDASQL provider. ODBC has been
    deprecated and will not be supported at some future date. See here:
    [url]http://msdn.microsoft.com/library/en-us/ado270/htm/ado_deprecated.asp[/url]

    I have noticed that the older ODBC attribute names still seem to work in
    OLEDB connection strings. I however, would advise you to use the newer OLEDB
    attribute names, as the ODBC names may become unsupported in a future MDAC
    release.

    HTH,
    Bob Barrows


    Bob Barrows Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139