[AccessD] VBE

> The object model is NOT VBA, it is a layer on TOP of VBA.
> An integrated set of objects that know how to be a Word
> document, a spreadsheet, or a database FE.  Once you
> reference the word object inside of Access, you have the
> same capabilities that you have inside of Word directly.
> Reference that Word object inside of Excel and you have
> the same set of capabilities as you had in Access (or
> Word) - to manipulate DOCUMENTS.
> So, you have VBA which is the same exact set of keywords
> and structures. VBA is available from all of the Office
> applications.  Inside of each application, you have an
> object model which is NATIVE to that application, which is
> not part of VBA but is called from VBA.  AFAIK, these
> object models, Word, Excel, Access, PowerPoint etc are
> also available to call from VB (the REAL VB programming
> language).  Which further demonstrates the interface line
> which separates the Office Application object model from
> the VBA language.
>

Not just VB.  You can program the object model from many
different languages - any that speak COM (including PBWin of
course <vbg>). The Methods, properties etc remain exactly
the same. The language you use can be completely different
to VB/VBA.
--------------------------------------
   This Email Was brought to you by
               WebMail
    A Netwin Web Based EMail Client
  http://netwinsite.com/webmail/tag.htm