Re: ADO Connection problem when not logged in as an Admin

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I never said that there was a difference between ODBC ADO and OLEDB ADO. In
fact, I don't understand what you mean by that.

ODBC is for DAO and OLEDB is for ADO. ADO doesn't understand ODBC drivers;
however, there is a special OLEDB driver (MSDASQL or Microsoft's OLEDB
Provider for ODBC) that can make the connection between ADO and an ODBC
driver but using this special driver (automatically called by ADO when using
an ODBC connection string) add another level of overhead.

If you use OLEDB than use an OLEDB provider in order to have the best
performance and if you are using SQL-Server 2005 than use its native driver
for the same reason.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"aedwards via AccessMonster.com" <u11653@uwe> wrote in message
news:7dac8ecb24af1@xxxxxx
Hey thanks for your help. I didn't know there was a difference between
ODBC
ADO and OLEDB ADO. I thought there was just ADO (which by default used
OLEDB)
I changed the connection string and it's working fine.

It doesn't explain (at least to me) why it was working for Administrators
and
not for non-admins, but what the hey, it works, so I'm not complaining.

Thanks again

Aaron

Sylvain Lafontaine wrote:
It's because you have made some errors in your connection string: USER and
PASSWORD are not valid parameters for the old ODBC SQL Server provider; so
I
suppose that ODBC is reverting back to using Integrated Security for
everyone.

Take a look at: http://www.connectionstrings.com/?carrier=sqlserver

In the case of SQL-Server 2005, you can also use the new native provider:
http://www.connectionstrings.com/?carrier=sqlserver2005

Finally, I don't understand why you want to still use an ODBC provider
when
using ADO objects. You should use OLEDB instead for a better performance
and using ODBC should be reserved to DAO.

Hi,

[quoted text clipped - 16 lines]

Thanks.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-modules/200801/1



.

Relevant Pages

  • Re: Cannot display ODBC login prompt - want to connect without DSN
    ... ODBC was superseded thirteen years ago by OleDb: ... In this particular case, my program will conect to an Oracle database, but ... There does not seem to be a .NET provider for MS Access, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Regarding fastest database interaction with Oracle in VC++
    ... If you are using ADO, then you will have a Connection object. ... is a lightweight COM API that sits on top of OLEDB. ... If you install MDAC 2.8, it will install some providers for you. ... It will install the MS Oracle provider. ...
    (microsoft.public.vc.database)
  • Re: ADO connection with VBS to locally stored MS-Access database
    ... Even using of the OLEDB Jet provider is better, I do not see any confusion ... You could use ODBC or OLEDB syntax but in this case ADO will using ... > I am trying to connect to a local Access database via ADO and VB Script. ...
    (microsoft.public.data.ado)
  • Re: create a data provider
    ... You can write a OLE DB Simple Provider in VB6 by implementing the ... _too_ simple for consumers like Excel 2007. ... ODBC or OLEDB wrapper for an ADO.NETdataprovider. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Migrating ASP/MSSQL app from IIS 4 to IIS 6
    ... > No, it defaults to the MSDASQL provider, which is the provider for odbc. ... > So, if "EXECBOB" is the name of a system DSN, this statement will work. ... > "This is the default provider for ADO" ...
    (microsoft.public.inetserver.asp.db)