Remarks from the official documentation: The method may return zero, which indicates that the object does not provide any type information. 0: the object does not provide type information.1: the object provides type information.The Four Methods of the IDispatch Interface GetTypeInfoCount To understand how this works, let's explore the four methods of the IDispatch interface.

In plain English, the IDispatch interface is like a COM object's table of contents. Late binding support requires the COM object to implement the IDispatch interface. Not all COM objects support late binding. If VBA doesn't know how to handle method and property calls of late-bound objects at compile time, how in the world is it able to handle them at runtime? IDispatch: The Key to Late Binding This is why there is no IntelliSense with late binding. In fact, at compile time, VBA does not know what methods or properties the object even supports. VBA knows nothing about how to handle method and property calls to a late-bound object at compile time. Set xlApp = CreateObject('Excel.Application') An example of late binding ( object variable is declared As Object).

To use late binding, you define your object as a generic Object type. Note the difference between early and late binding has to do with how the object variable is declared ( As Excel.Application) and not how it is instantiated ( CreateObject()). Set xlApp = CreateObject('Excel.Application') An example of early-binding. You then define the object using a specific type: Dim xlApp As Excel.Application to add a reference to the COM object's library. To use early binding, you need to use Tools > References. There are two primary ways to interact with COM objects from VBA:

Vba implements example