The information in this article applies to:
SYMPTOMSOn computers that have both the VBA5 Extensibility library (vbeext1.olb) and the VBA6 Extensibility library (vbe6ext.olb), cross-process automation of the VBA5 Extensibility Object Model fails. In C++ applications, this appears as a failure of a IUnknown::QueryInterface call. In Visual Basic applications, this appears as the following error message: This problem only affects applications writing to the VBA5 Extensibility Model, and not the VBA6 Extensibility Model. CAUSEThis problem is caused by changes in the type information of the Extensibility Library between VBA5 and VBA6. RESOLUTIONIn order to work around this problem, applications should use late binding to make calls to the VBA5 Extensibility Model. For Visual Basic (VB/VBA) applications, this can be accomplished by changing the declaration for your VBProjects variable from:
to
For C++ application, this can be accomplished by using the IDispatch interface to search for and Invoke methods.
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. MORE INFORMATIONSteps to Reproduce BehaviorTo see the problem, add the following code to a Visual Basic project on a computer that has both Office 97 (VBA5) and Office 2000 (VBA6) installed:
To correct the problem, change the code to the following:
Additional query words:
Keywords : kbSDKVBA kbGrpDSO kbDSupport |
Last Reviewed: October 26, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |