FIX: IObjectSafety Implemented in Toolbar and CmDialog Controls (171831)


The information in this article applies to:

  • Microsoft Visual Basic Learning Edition for Windows 5.0
  • Microsoft Visual Basic Professional Edition for Windows 5.0
  • Microsoft Visual Basic Enterprise Edition for Windows 5.0
This article was previously published under Q171831

SYMPTOMS

When using the CmDialog and Toolbar controls on a HTML page you would get the warning that these controls are not safe for scripting.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been fixed in Visual Studio 97 Service Pack 2.

For more information on the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:

170365 INFO: Visual Studio 97 Service Packs - What, Where, and Why

For a list of the Visual Basic 5.0 bugs that were fixed in the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:

171554 INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2

MORE INFORMATION

You need to able to use the CommonDialog and Toolbar Control on HTML pages without getting the "safe for scripting" errors. Because of the IObjectSafety interface in these two controls, this error will not show up when using these controls on a HTML page. Changes to the controls were the following:

  • CommonDialog - Disable the ability to display a help file in safe mode.
  • Toolbar - Disable writing to the registry in safe mode.
Modification Type:MajorLast Reviewed:11/18/2003
Keywords:kbbug kbfix kbvbp500sp2fix kbVS97sp2fix KB171831
©2003 Microsoft Corporation. All rights reserved.