INFO: The Type of OCX Property in Typelib Should Match Its RetVal

• Microsoft Visual Basic Learning, Professional, and Enterprise Editions for Windows, version 6.0
• Microsoft Visual Basic Control Creation, Learning, Professional, and Enterprise Editions for Windows, version 5.0
• Microsoft Visual Basic Standard, Professional, and Enterprise Editions, 32-bit only, for Windows, version 4.0

SUMMARY

An ActiveX control can cause an unhandled exception in VB32.exe if the type of any of its Properties as specified in its ODL file differs from the actual type that the property handler returns.

MORE INFORMATION

For example, this will happen if, in an ActiveX control's type library, a property is marked as type String (VT_BSTR), and the Get method for this property returns an integer (VT_I4). This is because when Visual Basic calls IDispatch::Invoke() to get that property value, the control fills in the Result variant parameter of Invoke() with the type VT_I4, but Visual Basic believing it is a string (from the Typelib definition), tries to dereference the integer and hence the general protection (GP) fault. Visual Basic assumes that the type returned by Invoke() will be the same as the type stated in the type library.

This situation can be prevented by fixing the type library of the custom OLE control or the property handler for the related property, whichever is wrong.

Additional query words: kbVBp400 kbVBp500 kbVBp600 kbVBp kbdsd kbDSupport kbActiveX kbControl

Keywords : kbGrpVB
Version : WINDOWS:4.0,5.0,6.0
Platform : WINDOWS
Issue type : kbinfo