New project using Access 2003. DAO or ADO recommended now

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Seemed to be a design shift as new versions of access were developed.

On a new project using Access 2003 which design is better (required?) DAO or
ADO?

Thx
 
lowly-worm said:
Seemed to be a design shift as new versions of access were developed.

On a new project using Access 2003 which design is better (required?)
DAO or ADO?
Click to expand...

If your data store will be an .mdb file, I'd go with DAO, other
considerations being equal. It's more powerful and more efficient in
working with Jet databases. If you're creating an ADP, I'd stick with
ADO. If you're planning to work with an .mdb front-end but a SQL Server
back-end, it's not clear. My personal inclination would be to continue
to use DAO for the most part, only going to ADO where (maybe) it becomes
necessary. But that's at least partly because I'm much more comfortable
and conversant with DAO than I am with ADO. If you're an ADO maven, I'd
suggest you use what you know best in those circumstances.
 
OK Thanx very much !

Dirk Goldgar said:
If your data store will be an .mdb file, I'd go with DAO, other
considerations being equal. It's more powerful and more efficient in
working with Jet databases. If you're creating an ADP, I'd stick with
ADO. If you're planning to work with an .mdb front-end but a SQL Server
back-end, it's not clear. My personal inclination would be to continue
to use DAO for the most part, only going to ADO where (maybe) it becomes
necessary. But that's at least partly because I'm much more comfortable
and conversant with DAO than I am with ADO. If you're an ADO maven, I'd
suggest you use what you know best in those circumstances.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)
Click to expand...
 
Back
Top