ADO

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Dear All,

I have created a small application which has now reached a point where I need to write some VBA Code. I am familiar with DAO syntax and I feel a bit daunted by the small exposure I've had with ADO.
What's the real story behind ADO? And why shouldn't I continue using it?
Any comments greatly appreciated.
Thanks
Greg
 
Not sure what exactly you're looking for as "the real story behind ADO".

If all you're doing is using a Jet database (i.e.: your data is simply in an
MDB, as opposed to some external data source), there's no reason not to
continue using DAO. DAO was developed specifically for use with Jet
databases, and you should even experience slightly better performance. If
you're using Access 2000 or 2002, you'll need to set a reference to
Microsoft DAO 3.6 Object Library. (If you're not going to be using ADO,
uncheck the reference to Microsoft ActiveX Data Objects 2.1 Library while
you're at it)

You may find it informative to read what Michka has on this topic at
http://www.trigeminal.com/usenet/usenet025.asp

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)



Greg Horwood said:
Dear All,

I have created a small application which has now reached a point where I
Click to expand...
need to write some VBA Code. I am familiar with DAO syntax and I feel a bit
daunted by the small exposure I've had with ADO.
 
thanks for the reply. I only meant by 'the real story...' to express my frustration that I learn and am competent in one system, then it changes on me. Obviously using ADO instead of DAO 'future-proofs' the application to some extent, so I'll probably press on and use it.
Thanks
Greg
 
Actually, that's not true. ADO has already been superceded by ADO.Net, which
is another creature again.

I think it's a fair statement to make that as long as Jet databases (i.e.
..MDB files) are around, DAO will be as well.

--
Doug Steele, Microsoft Access MVP

(No private e-mails, please)


Greg Horwood said:
thanks for the reply. I only meant by 'the real story...' to express my
Click to expand...
frustration that I learn and am competent in one system, then it changes on
me. Obviously using ADO instead of DAO 'future-proofs' the application to
some extent, so I'll probably press on and use it.
 
Actually, that's not true. ADO has already
been superceded by ADO.Net, which
is another creature again.
Click to expand...

Yes, it was another in Microsoft's long history of "Access methods for the
foreseeable future" that were soon superceded. Actually, all those methods
are still around, but no longer considered "methods of choice".

Larry Linson
Microsoft Access MVP
 
Back
Top