[Mono-list] Am confused.
Martin Adoue
martin@cwanet.com
Tue, 17 Sep 2002 13:28:03 -0300
> VBA is basically a VBScript interpreter, linked to the application so
> that it knows about the program's object model, which interprets VBA
> scripts the user provides.
>
> As for the relationship between Access, Excel, and VBA, all Office apps
> expose an object model which can be scripted through COM, as described
> above. Access, Excel, et. al merely expose the object model so the
> script interpreter can operate. They accept scripts written in VBA (a
> superset of VBScript), but they can also be "scripted" through "normal"
> COM interop, allowing for control from C/C++, Perl, TCL/TK, and any
> other COM-supporting language.
Not quite. VBA (the language) *is* VB. It's not a subset like VBScript (a
different implementation with very similar sintax).
You seem confused with VBA the "platform", which enables your app to be
scripted from within, with a debugger, etc.
VBA in Office 97 = VB 5
VBA in Office 2k/XP = VB6