Greetings,
The best usage for ADO is for dealing with external data -- data that
does not reside in the Access mdb. It is possible, however, to use ADO
within the Access mdb project, but that would be a little more work than
using native DAO for manipulating data within the Access mdb.
The big thing with ADO is that it is like a translator system. You can
write Transact sql in ADO (sql for Microsoft Sql Server), or PL sql
(Oracle sql) or Jet sql (sql for Access mdb's) and read the results of
the data pull right into an Access mdb table.
Rich
*** Sent via Developersdex
http://www.developersdex.com ***