FIX: SendKeys Causes Erratic Mouse Behavior on IBM PS/2

Last reviewed: October 30, 1997
Article ID: Q79603
1.00 2.00 3.00 WINDOWS kbprg kbbuglist

The information in this article applies to:

- Standard and Professional Editions of Microsoft Visual Basic for

  Windows, versions 2.0 and 3.0
- Microsoft Visual Basic programming system for Windows, version 1.0 - Microsoft Windows version 3.0

SYMPTOMS

When a Visual Basic program executes the SendKeys statement on an IBM PS/2 computer, Windows behaves erratically when you move the mouse until it is shut down.

CAUSE

The erratic behavior is caused by continuous phantom mouse clicks and mouse movements.

STATUS

Microsoft has confirmed this to be a bug in Microsoft Windows version 3.0. This bug was corrected in Microsoft Windows version 3.1.

MORE INFORMATION

If you are running Microsoft Windows 3.0 on a PS/2 computer and you press the NUM LOCK key while moving the mouse, the mouse events become erratic. The Visual Basic SendKeys statement affects the NUM LOCK key, so this problem results -- just as if NUM LOCK were pressed.

When you move the mouse, phantom Click events result in symptoms such as applications unexpectedly launching, or the mouse pointer jumping around the screen.

This problem has been reported to happen on the IBM PS/2 Model 50, Model 50z, Model 60, and Model 80.


Additional reference words: noupd 1.00 3.00 3.10 NUMLOCK
KBCategory: kbprg kbbuglist
KBSubcategory: PrgCtrlsStd
Solution Type : kbfix


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