DAO - singlethreaded - only one connection at a time - sometimes faster than ADO
ADO - multithreaded - can handle multiple connections - pretty fast for SQL and what not if you write it efficiently
big advantage for DAO is that if you use it in an application, where it is the only connection being made to a data base (such as a Utility saving it's settings to a database using DAO) it's rather fast.
big advantage of ADO, ADO is very useful with dealing with applications that require multiple connections, for example A serverside webapplication may load several peices of data from a database using multiple recordsets on a single connection, but then you would need to allow multiple instances for every connection made from the number of visitors to the site.
I personally find DAO a lot more straightforward and easier to use for manipulating data in different ways. Like when several calculations need to be made on different recordsets and SQL wont cut it, or it would just be too complicated, I find DAO very useful for this.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.