Re: DAO vs ADO

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Depending on how you're connecting to SQL Server, yes, it might make sense
to use ADO.

I've written applications where my communication to SQL Server was all done
through pass-through queries: no linked tables. Since pass-through queries
are not updatable, I used ADO to run the Update, Delete and Append queries
to update the database.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"Gary S" <GaryS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8CD62AAB-0E71-4FBE-A36E-3C7291A955AD@xxxxxxxxxxxxxxxx
Doug,
You mention it might make sense to use ADO
over DAO when connecting with certain dbms,
does that include SQL Server?
--
Thanks for your help!
Gary S


"Douglas J. Steele" wrote:

As Dave mentioned, DAO is alive and well. In fact, it's ADO that's no
longer
supported: it was replaced by ADO.Net, which is quite different (and
which
can't be used by Access).

DAO was designed specifically for use with Jet databases (i.e.: mdb, mde,
accdb or accde files). ADO, being a generic interface, isn't as quick
(nor
as capable) in that situation, although it might make sense if you're
connecting to other DBMS.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"Gary S" <GaryS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8370231C-F3BA-47FF-A124-FA05260068A7@xxxxxxxxxxxxxxxx
I have a general question about DAO vs ADO.

It is my understanding ADO is the way to go and
DAO will eventually not be supported. But when
I look at coding examples at various web sites
that give examples of code, it is usually DAO.
Am I mistaken about DAO phase out? Please help me
understand.
--
Thanks for your help!
Gary S





.

Relevant Pages

  • Re: Text of Startup Option Application Title
    ... This is a quote from Mary Chipman, SQL Server MVP, ex-Access MVP, and author ... DAO was designed, customized, and tweaked specifically for the Jet ... ADO was designed as a general-purpose data access wrapper around OLE ...
    (microsoft.public.access.formscoding)
  • Re: DAO vs ADO
    ... ADO ... > extra overhead retrieving metadata from the server for each query. ... > but I feel DAO is not as unsuitable as is often assumed. ... and ADO when working with SQL Server data. ...
    (microsoft.public.access.conversion)
  • Re: Connecting to a SQL Server 2005 using VBA and ADO
    ... dao should work just fine.... ... the above example when using sql server, or a plan Jane un-split database, ... I would not use findfirst even when not using sql server unless the data set ... Microsoft since they now seem to be favoring ADO. ...
    (microsoft.public.access.formscoding)
  • Re: DAO vs ADO
    ... The best rule of thumb to go by is: use DAO when working with local ... Access/Jet objects, and ADO when working with SQL Server data. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: DAO vs ADO
    ... The best rule of thumb to go by is: use DAO when working with local ... Access/Jet objects, and ADO when working with SQL Server data. ...
    (microsoft.public.access.conversion)