Microsoft KB Archive/140206

= BUG: OLE 16-bit Controls Halts System Painting to the Screen =

Article ID: 140206

Article Last Modified on 8/18/2005

-

APPLIES TO


 * Microsoft Visual Basic 4.0 Professional Edition
 * Microsoft Visual Basic 4.0 16-bit Enterprise Edition
 * Microsoft OLE Control Developer's Kit (CDK)
 * Microsoft Visual C++ 1.5 Professional Edition
 * Microsoft Visual C++ 1.51
 * Microsoft Visual C++ 1.52 Professional Edition
 * Microsoft Windows for Workgroups 3.11

-



This article was previously published under Q140206



SYMPTOMS
Opening any menu of a program created in the 16-bit edition of Visual Basic, version 4.0, containing the 16-bit OCX controls listed below or any control using the 16-bit edition of the Microsoft OLE Control Developer's Kit (CDK) shipping with Microsoft Visual C++ for Windows, version 1.5x stops the system from painting to the screen when running Microsoft Windows for Workgroup version 3.11. Any programs running in the background in addition to the Visual Basic program still run, however, the screens of these background programs are not repainted. Clicking near the menu to close the menu resumes screen painting. This behavior only occurs when running Windows for Workgroups 3.11 and is limited to the following controls:   Custom Control Name                    File Name ---

Desaware Animated Button Control     ANIBTN16.OCX MicroHelp Key State Control          KEYSTA16.OCX Microsoft Data Bound List Controls   DBLIST16.OCX Microsoft Grid Control               GRID16.OCX Microsoft Masked Edit Control        MSMASK16.OCX Microsoft Multimedia Control         MCI16.OCX Microsoft Outline Control            MSOUTL16.OCX Pinnacle-BPS Graph Control           GRAPH16.OCX Sheridan 3D Controls                 THREED16.OCX This behavior does not occur with internal controls or user-created controls.



STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.



Steps to Reproduce Problem

 * 1) In the Accessories group of Program Manager, double-click the Clock icon to start the Clock program.
 * 2) On the Settings menu, click Digital to change the Clock Settings to Digital.
 * 3) Move the Clock window to the lower-right corner of your screen. The Clock Window must be visible while Visual Basic is running.
 * 4) Start the 16-bit version of Visual Basic 4.0, or if it is already running, click New Project on the File menu.
 * 5) From the toolbox, add one of the 16-bit controls listed in the Symptoms section to Form1.
 * 6) Press the F5 key to start the Visual Basic program. Make sure both the Visual Basic program and the Clock program are running.
 * 7) Open the system menu by pressing ALT+SPACEBAR. The clock stops. When you click near the system menu to close the menu, the clock displays the current time.

Additional query words: kbi6bitonly kbVBp400bug kbVC150bug kbVBp kbdsd kbDSupport

Keywords: kbbug kbfix KB140206

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.