FIX: ARROW and TAB keys Stop Working in MDI Child Form (145677)
The information in this article applies to:
- Microsoft Visual Basic Enterprise Edition, 16-bit, for Windows 4.0
This article was previously published under Q145677 SYMPTOMS
When you have an MDI parent form with a toolbar and one MDI child form,
pressing a toolbar button can prevent the arrow keys and tab key from
functioning as cursor navigation keys on the MDI child form. You can still
type text into the text boxes on the child form, but the cursor can be
moved only by using the mouse pointer.
CAUSE
The toolbar control is capturing all navigation key events, preventing the
text box controls on the MDI child form from processing them.
RESOLUTION
To work around this problem, force the toolbar to lose focus. This will
prevent the toolbar from trapping the navigation key events. Add the
following code to the MouseUp event of the toolbar control:
Private Sub Toolbar1_MouseUp(Button As Integer, Shift As Integer, _
x As Single, y As Single)
Me.SetFocus
End Sub
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 Basic
5.0 and 6.0.
Modification Type: | Minor | Last Reviewed: | 1/8/2003 |
---|
Keywords: | kbbug KB145677 |
---|
|