And the heavy hitters over on the Access newsgroup suggest that for a Jet to
Jet application, ADO may have a performance hit that DAO doesn't have.
Pardon me for possibly using the wrong words here, but DAO is native to Jet
( the built-in database engine for VB and Access). ADO is a very smooth and
faster (in my limited experience) successor to ODBC but is still extra
overhead when Jet is manipulating Jet data.
As usual, your mileage may vary. And if I've led you astray here, will
someone please correct me?
> Dear all,
> Where I can find information, articles or examples of how to create a
> visual basic application that works with an access 2000 database placed in
> the server and the client apps ineach workstation of the LAN ?
> I need info about writing in the access database simultaneously from 2
> workstation using ADO.
> Thanks to all.