Ado or Dao

[JRB]

When creating a new db in Access 2000, is it better to use ado instead of
dao? I already have tons of code in personal library files and dread
rewriting all of it.

If the db will never be used with SQL Server, does it matter. Do Access
versions later than 2000 support dao. And how stable is it in Access 2000.

Thanks.

 

[Scott McDaniel]

When creating a new db in Access 2000, is it better to use ado instead of
dao? I already have tons of code in personal library files and dread
rewriting all of it.

Either one. Many people use only DAO, since it's "native" to Access/Jet (and
seems to be faster). You can use both, however, in the same project as long
as you disambigulate the references.

NOT Dim dbs As Database
INSTEAD Dim dbs As DAO.Database

NOT Dim rst As Recordset
INSETAD Dim rst AS ADODB.Recordset

If the db will never be used with SQL Server, does it matter. Do Access
versions later than 2000 support dao. And how stable is it in Access 2000.

So far, all versions "support" DAO, as long as you set a reference to it. If
I were you, I'd move up to Access 2002 OR back to Access 97. 2002 is
considered more stable than 2000. Do a google on "ms access 2000 stability"
or some such and you'll see what I mean.

 

[Joshua A. Booker]

Doug,

I concur. Is it also true that DAO performs better than ADO on Jet
databases? And did Microsoft say they will be making no new versions of
Jet? Does that mean they will be doing away with Jet?

TIA,
Josh