ADO vs DAO

[David W. Fenton]

=?Utf-8?B?SmFtaWUgQ29sbGlucw==?=

P.S. don't you think it's time we all moved on and start embracing
ACE as being the future and stop calling it 'Jet'? Jet is now
deprecated, has been for years, and ACE is the last hope for
Access and DAO. Make the most of it, people!

The problem is that the only version of Access that supports ACE is
really bad.

 

[AlexM]

Man what a storm.

ADO vs DAO is the old question.
Do you like chicken or turkey?
Sometimes I like chicken and sometimes I like turkey.

DAO is good if you are accessing Access linked tables in an application that
is used by few users.
DAO principles are only used in Access and there is very little reusable
code and development methodology you can apply outside MS Access.

ADO coding principles are used everywhere else where data is access whethere
it be Access, SQL server, Oracle etc.
ADO recordset object has far more functionality.

And no ADO is not deprecated, ADO.NET is ADO in .NET framework.

ADO requires more coding and you have to control aspects of your application
that Access hides from you.

So depending on how much time you have and what your starting application
looks like you might use ADO or DAO.

One is not better than the other.
Both have their appropriate applications.

Good luck.