[dba-Tech] SharePoint, Access, InfoPath

Even after reading a couple of overviews, I still remain a little (a lot?)
vague on how these components. From what I can see, SharePoint as sort of
portal within an organization, and may contain any number of folders and
documents and Access databases and something called SharePoint lists,
whatever they may be.

During a quick visit to a colleague's office, I got a quick glance at an
InfoPath front end which appeared to be talking to an Access back end. The
InfoPath forms looked a lot more like typical documents than like
traditional Access forms. I was told that everyone in the organization had
access to InfoPath, and gathered that part of doing things this way was to
facilitating document sharing and workflow; that instead of a bunch of
emails sent back and forth with attached documents, that this approach
provided a single source for the current revision of any document.

It has been said repeatedly on this list and/or our AccessD list that
SharePoint will not accept an Access db that contains VBA code (or perhaps
will accept it but not be able to execute any VBA contained therein.
Although I have InfoPath 2007 installed, I don't think I have fired it up
more than once, if that, so I have no inkling as to its capabilities and
limitations. Could it be that SharePoint will accept InfoPath forms
containing code, but not Access forms?

I ask anyone with knowledge of these three products working together to
offer an overview and any additional things that would help me grasp this
technology stack. (Such as, given that an Access db lives somewhere in
SharePoint, how did it get there in the first place, and assuming that it
subsequently evolves - new table or query added, etc. - how is it updated?
I sure hope that structural changes are not performed on the production
version of the Access db.

Thanks for any light you can shed.

-- 
Arthur
Cell: 647.710.1314

Prediction is difficult, especially of the future.
  -- Niels Bohr