I did some tests to see if ADO 2.0 is really faster that DAO 3.5 and I gotta
tell ya -- DAO whooped ADO's {*filter*}in EVERY test I ran. I did a MoveLast test
against an Access 97 database and a SQL Server 6.5 database and it took ADO
17 seconds to do what DAO did in less than 1 second. I also looped through
all the records in each database and what took DAO 3 seconds took ADO 33
seconds.

I feel like I'm missing the boat here in terms of capitalizing on the speed
of ADO. Can anyone shed some light on the subject?

There are some testing results (VB5 v. VB6 v. VC++ v. VJ++, DAO v. ADO v.
RDO) in the current issue of VBPJ you might want to check out. I don't have
the magazine with me right now, but I remember a title that said something
like "Don't count DAO out yet."

It does stand to reason that a direct native access method (DAO) would, on
average, be faster than a generic access method (OLEDB/ADO). Generic access
offers a different advantage...flexibility and a greater degree of
portability between different database systems. The question is which method
works best with the design you want to implement.

Frank Carr