DSN versus DSN-Less 2

[sheykc]

Does anybody know the pros and cons of using a DSN versus a DSN-less connection, when working with ADO in Visual Basic?

 

[Terpsfan]

A DSN-less connection is considered to be the preferred method because it is a faster and more efficient way to access the data source. If you use a DSN you must go through the additional ODBC layer in order to access the data store. If you use OLEDB then you are eliminating this layer. Since the connection absorbs a lot of resources, go with the faster method.

'For SQL Server
Dim objConn as ADODB.Connection
Form_Load()
Set objConn = New ADODB.Connection
objConn.Open "Provider = SQLOLEDB; Integrated Security = SSPI; Persist Security Info = False; Initial Catalog = databasename; Data Source = SQLServername"

'For Access
objConn.Open = "Provider = Microsoft.Jet.OLEDB.4.0; Data Source = databasefullpath"

 

[sheykc]

Do you know if

SQLOLEDB

will work with Sybase?

Shey

 

[Terpsfan]

SQLOLEDB is specific to SQL Server. I'm sure there is an OLEDB provider for Sybase. To find out if you have a Sybase OLEDB, open a VB project and then Add a Data Environment from the Project Menu. Then right-click the connection and then select properties. All of the OLEDB providers will be listed.

 

[sheykc]

Thanks for your help.

I have one more question though. I went to VB, added the Data Environment, etc---and I don't see an OLEDB for Sybase. However, I noticed the OLEDB for ODBC drivers. Is this the same thing as creating an ODBC connection? Will I still be going through the ODBC layer?

Shey

 

[100watt]

I am using "SQL Anywhere Studio 8"(Sybase) and the ODBC driver I used is "Adaptive Server Anywhere 8" and if you are using the connectionstring the provider would be "ASAProv".