Yes, similar problems experienced here.
After reading the duawamish examples, I tried upgrading from DAO to ADO. I
noticed a huge increase in realtime, and after investigating, found that
using DAO, a call to .openrecordset took on average 7ms, while using ADO, a
call to the .open method took 280ms (thats 40 times slower!). These
measurements were taken opening the same table in an Access DB in Win98 on a
I can only assume that when people say that ADO is quicker for the vast
majority of applications, they exclude applications where MS Access is used.
I am currently considering using both ADO and DAO in the same application -
using DAO for client-side caching (because of better real-time) and using
ADO for reading/writing to the DB (to make use of Transactions, and Shaped
cursors). Any opinions about whether this will work?
> I have just purchased VB 6 pro. The ADO's features are quite
>impressive. However when I connected a ADO Data Control to a Grid to pull
>table from an mdb.(The table was about 250 meg in size-LARGE) it took 20
>minutes for the program to display the records on the grid VS DAO Data
>which only takes 10 seconds to do the same thing. Does anyone know what is
>going on here ?
>Thanks for any suggestions