Implement the IObjectSafety interface of the control in VB,
To flag that the control is script safe and initialized securely.
Reference:
Http://www.cnblogs.com/JessieDong/archive/2009/12/07/1618762.html
It's all about the dangers of ActiveX, so why are XMLHttpRequest and MediaPlayer created in an ActiveX way, but no problem? Originally, this is because these ActiveX components declare themselves to be script-safe, and the intermediate security setting of IE, is to allow the scripting security of ActiveX creation, and do not warn.
How does ie know that a plugin is script-safe? It is through the following two methods. The first is to query whether the ActiveX component implements the IObjectSafety interface, and returns the script security, and the second is whether the query ActiveX component indicates that it is implemented in the component Category Manager of the Registry catid_ Safeforinitializing and CATID_SafeForScripting.
For more information, see the MSDN article:
About Iobject Safety Extensions for Internet Explorer
Safe initialization and Scripting for ActiveX Controls
VB IObjectSafety Interface