This is the recommended approach, linking the tables in the back end
(tables, relationships, and data) from the front end (queries, forms,
reports, macros, and modules)

This request really doesn't make sense... you don't "do Access applications
in ADO." ADO (ActiveX Data Objects) and DAO (Data Access Objects) are two
methods for doing I/O from Visual Basic for Applications (VBA) code to the
Tables in the database. But, very often, little or no access from VBA code
is needed, because you "bind" Forms and Reports to the database by
specifying a RecordSource. And, in any case, DAO is the "native language" of
the default Jet database engine, and is most probably a better choice for
any VBA access to the data that is required.

There's good information in various pages of http://www.mvps.org/access,
and at MVP Tony Toew's website http://www.granite.ab.ca/accsmstr.htm, and at
MVP Jeff Conrad's website
http://home.bendbroadband.com/conradsystems/accessjunkie.html. None of these
are "tutorials."

The "enterprise edition" of _Microsoft Access <version> Developer's
Handbook_, by Litwin, Getz, et al, published by Sybex, has good information
on multiuser Access applications as well as Access client-server. It is
intended for Intermediate to Advanced developers. An introductory PowerPoint
presentation that I did, some time ago, for my user group is posted at
http://appdevissues.tripod.com (if the site is still active).

 Larry Linson
 Microsoft Access MVP