PRB: Accelerator Keys Fail to Work in MDI Child Forms (192183)
The information in this article applies to:
- Microsoft Visual Basic Learning Edition for Windows 5.0
- Microsoft Visual Basic Learning Edition for Windows 6.0
- Microsoft Visual Basic Professional Edition for Windows 5.0
- Microsoft Visual Basic Professional Edition for Windows 6.0
- Microsoft Visual Basic Enterprise Edition for Windows 5.0
- Microsoft Visual Basic Enterprise Edition for Windows 6.0
This article was previously published under Q192183 SYMPTOMS
In MDI child forms, accelerator keys such as CTRL+TAB, CTRL+F6, and CTRL+F4
will not work when the focus is set to the following controls:
Combobox
Tabstrip
Slider
Listview
Treeview
MaskedEdit Control
DBGrid
DBCombo
DBList
few non-intrinsic controls.
The accelerator keys will work for the following controls:
CommandButton
Textbox
Listbox
Picturebox
Checkbox
OptionButton
Vertical Scroll Bar
Horizontal Scroll Bar
DriveListBox
DirListBox
FileListBox
RESOLUTION
The workaround is to trap the keys in the KeyDown event of each child form
and to simulate the right behavior by sending the WM_SYSCOMMAND message.
See the MORE INFORMATION section below for a step-by-step example that
describes how to implement this workaround if many forms are present in a
project.
STATUS
This behavior is by design.
REFERENCESFor additional information, click the article numbers below
to view the articles in the Microsoft Knowledge Base:
189779 BUG: Enabling Accelerator Keys in Visual Basic ActiveX Controls
99688 How to Trap Keystrokes in the Form Instead of Form's Controls
113328 PRB: Form KeyDown Displays Inconsistent Behavior
189616 BUG: DateTimePicker Overrides ALT+F4 Key Combination
149273 BUG: Form Key Events Fire Twice with Some Controls
Modification Type: | Major | Last Reviewed: | 5/13/2003 |
---|
Keywords: | kbprb KB192183 |
---|
|