PRB: Object Required Error with VBScript in IE 3.x, 4.0

Last reviewed: October 3, 1997
Article ID: Q157907
The information in this article applies to:
  • Microsoft Visual Basic, Scripting Edition, versions 1.0, 2.0, 3.0

SYMPTOMS

Using Visual Basic Scripting Edition (VBScript) to reference ActiveX controls in Internet Explorer 3.x (IE3) or Internet Explorer 4.0 (IE4) could cause an "Object Required" error.

CAUSE

If security is set to HIGH in IE3 or the security for the current zone is set to HIGH in IE4, and your controls are not marked safe for scripting, then you will receive the "Object Required" error. This occurs even if the controls have already been installed on your machine.

RESOLUTION

By changing the security setting to MEDIUM in the Security page of the property settings for IE3, you may be able to resolve your problem. On the Security page, click the Safety Level button to change the setting from HIGH to MEDIUM. Once you have changed the security level, you should get messages indicating that a potential security problem exists. Accept all the warnings, and your script should work.

STATUS

By default, security is set to HIGH in Internet Explorer 3.x.

The default settings for Internet Explorer 4.0 are as follows: "Local intranet zone" and "Internet zone" set to MEDIUM "Trusted sites zone" set to LOW "Restricted sites zone" set to HIGH

Keywords          : PrgCtrlsStd kbother kbprb
Version           : Win:1.0,2.0,3.0
Platform          : WINDOWS


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 3, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.