P.S. I'm a beginning Access VBA user, but an intermediate Excel VBA user.
Under time pressure I've decided to "drive the car" from within Excel rather
than Access (since I'm dealing with data analysis and interpretation rather
than database storage) and to focus on ADO- rather than DAO-based
connections between the two applications (since ADO seems to be the wave of
the future). Is this reasonable?

Yes, it is reasonable and wise - DAO is now basically
obsolete. I also use ADO often to import Access (and
other db) info into Excel for more intensive numerical
analysis. With ADO you can even write Excel User
Functions based on your Access data.

For info on ADO you can go to the MSDN Library Data Access
Technologies section:
http://msdn.microsoft.com/library/default.asp?
url=/nhp/default.asp?contentid=28001860

-----Original Message-----
P.S. I'm a beginning Access VBA user, but an intermediate
Excel VBA user.
Under time pressure I've decided to "drive the car" from
within Excel rather
than Access (since I'm dealing with data analysis and
interpretation rather
than database storage) and to focus on ADO- rather than
DAO-based
connections between the two applications (since ADO seems
to be the wave of
the future). Is this reasonable?


.