The information in this article applies to:
SYMPTOMSWhen calling a method in an ActiveX control built with Microsoft Foundation Classes (MFC), if there is an out parameter in the method with a type variant, Visual FoxPro returns a type mismatch error. CAUSEWhen you call a method in the ActiveX control and pass it a variable by reference to receive a parameter value back from the ActiveX control, Microsoft Visual FoxPro seems to use a data type of BSTR. If the ActiveX method's parameter is defined as a Variant in the MFC based ActiveX control, this causes MFC to try and coerce the data types to match by using the VariantChangeType function. This function returns the type mismatch error. RESOLUTIONControls built with the ActiveX Template Library (ATL) do not have this problem. If you build the control in Microsoft Foundation Classes (MFC), avoid using out parameter data types of variant. STATUSThis behavior is by design. MORE INFORMATIONSteps to Reproduce BehaviorCreating the Server
Creating the Client
When the button is clicked, the type mismatch error occurs.REFERENCES
For additional information, please see the following articles in the
Microsoft Knowledge Base:
Q146219 How To Register an ActiveX Control (.ocx) Manually Q139154 OLE Control Licensing in Visual FoxPro Additional query words:
Keywords : kbVFp kbVFp500 kbVFp500a kbVFp600 kbGrpFox FxotherGeneral |
Last Reviewed: July 13, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |