Howdy! I have a question regarding the performance of opening a
recordset via 2 different methods. Are there any performance
differences between opening a recordset by directly using an ADO
connection versus opening a recordset through Access linked tables?
Besides performance, are there other advantages/disadvantages between
the 2 different methods? The data I am connecting to all resides in
an Access database. I am asking more out of curiosity than anything.
Thanks.

Vincent

Hi vincent,

Here are some thoughts about ADO and its usage. ADO is best suited for
interfacing between Access and Sql Sever (or Oracle). It has more
flexibility/power than ODBC. But for mdb to mdb, you will have at least
the same if not better performance using linked tables and way simpler
usage. What makes ADO a superchamp over ODBC between sql server and an
mdb is that ODBC is a continuous connection with lower bandwidth than
ADO. An ADO connection -- to a server DB that is --, on the other hand,
only exists while you are manipulating data. You pull/push data and
then disconnect. This is the more ideal paradigm (the paradigm on which
ADO.Net is based - disconnected recordsets). with mdb's - even if the
backend lives on a server - it is not part of the server. An mdb on a
server is just a file on a server because mdb's are file based databases
- not server based. So a linked table is not a continuous connection to
a server. It is a continous connection to a file - a small file
(compared to a sql server DB).

If you want to practice with ADO - that would be the only reason I can
think of to use ADO between mdbs. It is a great technology, but my line
of thinking is that whatever environment you are using for production -
make it as simple as possible. DAO is simpler than ADO for mdb to mdb,
but ADO is simpler for mdb to sql server (because you don't have to
conjure up as many workarounds for functionality which DAO does not have
to interface with server based DBs).

Rich

*** Sent via Developersdex http://www.developersdex.com ***

Yes you would be better off with linked tables. That way you could
avoid having to write code to connect to the database and pull back
records.

For FREE Access ebook and videos click here
http://access-databases.com/ebook



On 22 Jan, 15:57, Vincent <animedrea... (AT) verizon (DOT) net> wrote: