Ask a Question related to ASP Database, Design and Development.
-
Bob Barrows #1
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
-
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... -
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... -
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... -
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... -
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. -
Aaron Bertrand - MVP #2
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
-
Luis #3
Re: sqloledb Provider and dbmssocn
"Aaron Bertrand - MVP" <aaron@TRASHaspfaq.com> wrote in message news:<eSbM8yOXDHA.1900@TK2MSFTNGP10.phx.gbl>...
Thanks.> I've always used just Network. (See [url]http://www.aspfaq.com/2126[/url] and
> [url]http://www.aspfaq.com/2082[/url])
>
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
-
Bob Barrows #4
Re: sqloledb Provider and dbmssocn
Luis wrote:
The MSDASQL provider is also known as the "Microsoft OLEDB Provider for>
> 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
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



Reply With Quote

