PRB: FlexGrid Control Doesn't Trap Arrow Keys

Last reviewed: July 23, 1997
Article ID: Q171733

The information in this article applies to:

Microsoft Visual Basic Professional and Enterprise Editions for Windows, version 5.0

SYMPTOMS

The KeyUp and KeyDown events of the Flexgrid control do not trap the Arrow keys. This affects the arrow keys on the numeric keypad as well as the "stand-alone" arrow keys.

CAUSE

The Flexgrid control responds to the arrow keys to change the selection, therefore they are not passed to the key events.

RESOLUTION

There are no workarounds at this time.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Behavior

Turn the NumLock setting on your keyboard off.

Create a new Visual Basic project, Standard Exe.

Place a FlexGrid control on the new default form.

In the KeyUp event of the FlexGrid control, place the following code:

      Msgbox KeyCode

Run the form, and click on the FlexGrid control.

Press any arrow key and note that the message box does not appear.

Press any other key and observe that the message box appears. (Hint: use the mouse to close the message box.)

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