Microsoft KB Archive/171831

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 11:05, 21 July 2020 by X010 (talk | contribs) (Text replacement - """ to """)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


FIX: IObjectSafety Implemented in Toolbar and CmDialog Controls

Article ID: 171831

Article Last Modified on 11/18/2003



APPLIES TO

  • Microsoft Visual Basic 5.0 Learning Edition
  • Microsoft Visual Basic 5.0 Professional Edition
  • Microsoft Visual Basic 5.0 Enterprise Edition



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.


Keywords: kbbug kbfix kbvbp500sp2fix kbvs97sp2fix KB171831