Can I use ADO or DAO in access 97? THanks.

A97 knows all about DAO.

Be sure to use the version 3.5x library, not the 3.6 library (which is
designed of JET 4.)

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

" -Hillary" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Can I use ADO or DAO in access 97? THanks.

" -Hillary" <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> Can I use ADO or DAO in access 97?

DAO is what you should use, but ADO *can* be used, just not very
well. A97 does not have the built-in ADO support that A2K and later
had.

It would be a very unusual circumstance where there was a
justification for using ADO in A97.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

DAO is simpler, quicker and easier to code.

ADO is often needed to link to other databases like db2

Regards.
Tom Bizannes
Microsoft Access Development
http://www.smartbiz.com.au

"SmartbizAustralia" <(E-Mail Removed)> wrote

> DAO is simpler, quicker and easier to code.

I agree.

> ADO is often needed to link to other databases like db2

Really? I thought there were ODBC drivers for "databases like db2" that
worked very nicely. I've been linking to tables in server databases with
ODBC drivers since back in the days of Access 2.0, and found that most (and
I believe that includes DB2) are ODBC-compliant.

I'd guess, considering databases still in use, but not updated in recent
years that the universe of ODBC-compliant databases would be greater than
the universe of OLEdb-compliant databases.

Larry Linson
Microsoft Access MVP