You can (and should) use an ADO recordset if the form is based on an ADO
recordset, such as if you use an ADP instead of an MDB.
But if you use regular Access tables, in a normal Access form, you will have
a DAO recordset, because Access itself uses DAO.
About 7 years ago, Microsoft was trying to wean Access users away from DAO,
in the misguided hope that we would all convert to SQL Server back ends.
That's what all the hype was about, including ADPs. Today, ADO is dead,
replaced by the quite different ADO.NET in environments outside of Access,
and ADPs are not well supported in A2007 and Microsoft is suggesting you
don't use those either:
http://www.amazon.com/exec/obidos/t...104-9274862-0445505?v=glance&s=books&n=507846
You should also be aware that MS restored DAO as a default reference in
A2003, and continues to use it in A2007.
So, the information you have been given is:
a) out of date by 2 versions, and
b) never was right in the first place.
DAO is the native library in Access. When you create a query, Access is
using DAO. When you open a form bound to an Access table, Access is using
DAO. The "A" in ADO *is* Access, i.e. the library is designed to expose the
data objects in Microsoft Access.
More info about the libraries:
http://allenbrowne.com/ser-38.html