Re: [Access2003, VBA] Use DAO or ADO?

"Albert D. Kallal" <PleaseNOOOsPAMmkallal@xxxxxxx> wrote in
news:cXB3l.67200$JU5.3833@xxxxxxxxxxxx:

"David W. Fenton" <XXXusenet@xxxxxxxxxxxxxxxxxxx> wrote in message
\

Er, what? I thought ADO was a good idea only for SQL Server? If
you want the convenience of linked tables, you're going to use
ODBC, whatever the back end.

True the tables are linked by odbc, but you still have to
choose a data object model for your reocrdsets. So, a lot of
people when using linked tables STILL prefer ado because that's
what they are comfortable with.

Access developers? I don't think so, unless they spend most of their
time with ADPs.

You can use CurrentProject.Connection when you have linked tables
to a jet backend to open a ado recordset.

Why would you want to do so?

While there is some advantages when using ADO with sql server,
oracle (at least ones that provide a oleDB connection) there also
a good case to choose ADO if you plan to upgrade to sql server in
the future.

Why? If you're using ODBC, you gain exactly nothing.

And another great case is if your SAME application needs to work
with a jet file share for some customers, but other larger
customers want/need sql server and another wants to use MySql.

What? Sounds like a perfect place where Jet will be the best
interface, since you can use linked tables for Jet, and ODBC linked
tables for both SQL Server and MySQL.

So, ADO is a better abstraction and it is more data engine
neutral then DAO.

I think that's pure bull***. If you're using linked tables, then
Jet is involved, and it's just bloody silly to use ADO to work with
Jet, even if the back end is something other than Jet. If you're
using ODBC, then you're not communicating directly with the back end
tables.

ADO is fine for unbound apps, but it's not of much use in an app
with linked tables.

You could likely accomplish writing an application with dao that
works for the 3 above mentioned systems, but ADO does tend to
force you to be somewhat more data engine neural when you write
your sql statements.

I think that is, once again, completely BS.

Of course an ADP project is another matter, and you
MUST use sql server with a adp project.

And that's right where I started. ADO for ADPs, DAO for everything
with linked tables. If you're not using linked tables, then you
really oughtn't be using Access at all. In other words, DAO makes
more sense for nearly every realistic scenario. ADO makes little
sense for any Access development.

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

Loading