PRB: Launching VB5 ActiveX Documents from Internet Explorer

 Last reviewed: July 31, 1997
Article ID: Q168431
The information in this article applies to:
  • Microsoft Visual Basic Professional and Enterprise Editions for Windows, version 5.0

SYMPTOMS

When browsing to an ActiveX Document using Microsoft Internet Explorer, the document will fail to load the associated VBD file correctly. Instead, Microsoft Internet Explorer will display the following message: 

   "Opening:
   <filename> from <URL>

   Some files can contain viruses or otherwise be harmful to your
   computer. It is important to be certain that this file is from a
   trustworthy source.

   What would you like to do with this file?"
The user is presented with a choice of Opening or Saving the VBD file. If the user selects Open, the Open With window is displayed asking which application should launch the file. None of the applications listed, including Microsoft Internet Explorer, will successfully launch the VBD file.

CAUSE

The Setup Wizard for Microsoft Visual Basic 5.0 creates a set of files to be used for Internet download of ActiveX Documents. These files include a cabinet (CAB), VBD, and a hypertext-markup HTM file.

Unfortunately, without changes to the HTM file, an ActiveX Document will not launch correctly when a user browses to the HTM file using Microsoft Internet Explorer 3.x.

RESOLUTION

Below is a sample of an original HTM file created using the Microsoft Visual Basic 5.0 Setup Wizard. Following the example, is another sample that shows a working HTM file.

Example 1 - Original HTM File

   <HTML>
   <OBJECT ID="SampleDoc1"
   CLASSID="CLSID:11111111-1111-1111-1111-111111111111"
   CODEBASE="Project1.CAB#version=1,0,0,0">
   </OBJECT>

   <SCRIPT LANGUAGE="VBScript">
   Sub Window_OnLoad
       Document.Open
       Document.Write "<FRAMESET>"
       Document.Write "<FRAME SRC=""SampleDoc1.VBD"">"
       Document.Write "</FRAMESET>"
       Document.Close
   End Sub
   </SCRIPT>
   </HTML>

Example 2 - Changed HTM File

   <HTML>
   <OBJECT ID="SampleDoc1"
   CLASSID="CLSID:11111111-1111-1111-1111-111111111111"
   CODEBASE="Project1.CAB#version=1,0,0,0">
   </OBJECT>
   <SCRIPT LANGUAGE="VBScript">
   Sub Window_OnLoad
       Location.Href = "SampleDoc1.VBD"
   End Sub
   </SCRIPT>
   </HTML>
The changes to the Window_OnLoad procedure allow the VBD file to be launched successfully, thus the ActiveX Document will initialize and display within Microsoft Internet Explorer.

To convert an HTM file created with Setup Wizard, do the following:

  1. Make a copy of your original HTM file.

  2. Open the Original HTM file into Notepad.

  3. Remove the lines in the Window_OnLoad procedure. Make note of the VBD filename on the third line of the procedure.

  4. Place the following code within the Window_OnLoad procedure: 

          Sub Window_OnLoad
          Location.Href = "FILENAME.VBD"
      End Sub

    where "FILENAME.VBD" must be replaced with the name of your VBD
    (including quotation marks).

  5. Save the HTM file.

STATUS

Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. 

Keywords          : AXSDKDocObjects vb5all kbtool kbprb
Technology        : kbole kbInetDev
Version           : 5.0
Platform          : WINDOWS
Issue type        : kbprb

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

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: July 31, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.