ADO and Multithreading

It is not clear what level of threading support ADO provides on top of the normal ODBC driver support for the JET database engine. Does ADO provide any additional multithreading capability or does it rely entirely on the JET ODBC driver? In terms efficiency, ADO seems to add another layer to the ODBC driver (by using the OLEDB interface for ODBC), generally making it a less efficient choice.
Besides the fact that ADO is Microsoft's latest idea, are there any speed or multithreading benefits or potential benefits to sway someone to use ADO vs. normal ODBC and what are they?

[Wayne Fuller]

It is not strictly used for Jet databases, it can be used for any database that uses ODBC. Yes it is an extra layer so it will be slower, but have you ever used the ODBC API. In my opinion it is hard to use. About the multithreading support, I know ADO supports multithreads but I am not sure if they use multithreads. I have used MFC's CDatabase and CDaoDatabase, and I like ADO much better. If you are familiar with COM programming, I think ADO is the way to go.

Wayne

[ksheeraj]

Hi ,
Question.
Why ADO is 10times slower then DAO.Only for MS-ACCESS database.
Ksheeraj

39639,Leslie St.
Apt #157
Fremont USA 94538

[Wayne Fuller]

One reason is DAO does not have to go through the ODBC driver to get to the database like ADO does. You can specify a file with DAO and get rid of at least two layers. But DAO can only be used with Jet databases. If you are strictly using Jet databases and C++, then DAO may be the way to go. But Microsoft has already stated that since they are now pushing ADO, that they will no longer work on DAO. So the version as of right now will be the last.

Hope I answered your question,

Wayne