Cindy,
I hardly believe you need to go through VBA to access Words COM Interface.
Words COM interface is defined in MSWORD9.OLB (for Word 2000). As VBA is a
product integrated into Word and is not application specific in that way, I
would be very surprised if the calls goes through VBA. That would mean a
call to Word would go to VBA which in turn would call Word. That would be
very, very unefficient. VBA is actually a product that you can licence and
use in products that you develop by your self. If you take a look at this
site you might understand why I don't believe VBA is involved:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/office97/html/SF7BC.asp
As is states "Visual Basic in Microsoft Excel can access objects in other
applications that support OLE Automation, and in fact, Visual Basic uses OLE
Automation to call Microsoft Excel properties and methods" you may
understand why I have hard to believe the calls goes through VBA.
If you read the article above perhaps I can explain a few things. The 'vtbl'
is a short for Virtual Allocation Table, also often called V-table. It can
be treaded as list of function pointers. Using the vtbl is very fast as you
work directly with function pointers. If you use the IDispatch interface
your method name will be searched in the 'method table' (like a table of
contents) and from there get the function pointer. It's like when you want
to find a chapter in a book, if you use the vtbl you already know on which
page it is and goes directly to that page but with IDispatch you must first
look in the table of contents to find out on which page the chapter is and
then go to that page.
Regards,
Lars-Eric