ADO vs DAO Recordsets

[Jay]

Hi all,

I have a question regarding the use of ADO vs DAO recordsets.

Currently I'm using ADO Recordsets to transfer data from Access 97 to Excel.
You might ask, why ADO? The reason is that's what the code said to do:
http://support.microsoft.com/default.aspx?scid=kb;en-us;246335#XSLTH3133121122120121120120

The code worked fine for it's purpose, but I encountered one issue. To get
around it, I tried modifying the code to use DAO Recordset. Basically it was
a minor code change, nothing drastic.

But I was curious if there's any particular benefit to using ADO to perform
the task over DAO.

Thanks,
Jay

 

[Douglas J. Steele]

If you're only dealing with a Jet database (i.e. an MDB or MDE), then
there's no real advantage to ADO. DAO was designed specifically for use with
Jet databases. Being a more generic approach, using ADO adds unnecessary
additional levels of abstraction.

 

[David C. Holley]

Pretty much NO, however it gets into the ADO vs DAO debate which centers
around the preferred method. Being in the DAO camp, I only use DAO when
working with Access since its more or less native to JET - the engine
behind Access, not to mention that its been around much longer and to my
understanding ADO as originally envisioned is somewhat defunct. (Enough
disclaimers in there?) At any rate, if you're using sample code that is
ADO-based I would use it unless you're familar enough with DAO to conver
to DAO.