Access 2000 - Queries in code - ADO or DAO

If you are using Access' default Jet databases, there are many advantages to
continuing to use DAO:

-- DAO is the native language of Jet
-- DAO is faster with Jet than ADO
-- DAO is more complete for Jet than the
combination of ADO and ADOX

IMNSHO, there are few advantages to using ADO, but some are:

-- Accessing data in XML tables
-- Accessing other data in databases that
have an ADODB driver but no ODBC
driver available

others may be able to suggest additional reasons for using ADO. I would have
to have some _compelling_ need in order to use anything but DAO with a Jet
database.

Larry Linson
Microsoft Access MVP

"William Roberts" <wi*********@hotmail.com> wrote in message
news:0z*******************@nwrddc01.gnilink.net...

Hello
I am going to start making some of my queries in code. (VB in Access 2000) .. Should I use ADO or DAO? Does it make a big difference and why?

Thanks
William Roberts

Thanks Larry

"Larry Linson" <bo*****@localhost.not> wrote in message
news:Q_******************@nwrddc03.gnilink.net...

If you are using Access' default Jet databases, there are many advantages to continuing to use DAO:

-- DAO is the native language of Jet
-- DAO is faster with Jet than ADO
-- DAO is more complete for Jet than the
combination of ADO and ADOX

IMNSHO, there are few advantages to using ADO, but some are:

-- Accessing data in XML tables
-- Accessing other data in databases that
have an ADODB driver but no ODBC
driver available

others may be able to suggest additional reasons for using ADO. I would have to have some _compelling_ need in order to use anything but DAO with a Jet
database.

Larry Linson
Microsoft Access MVP

"William Roberts" <wi*********@hotmail.com> wrote in message
news:0z*******************@nwrddc01.gnilink.net...

Hello
I am going to start making some of my queries in code. (VB in Access

2000) .

Should I use ADO or DAO? Does it make a big difference and why?

Thanks
William Roberts