BUG: TabStop Property Does Not Work

• Windows CE Toolkit for Visual Basic 5.0, version 1.0

SYMPTOMS

Setting a controls TabStop property to False has no affect.

RESOLUTION

Try one of the following workarounds:

1. Use the LostFocus event of the control preceding the control to be skipped in the Tab order. In the LostFocus event procedure, set the focus to the next control in the desired Tab order.

   In the following example, there are three CommandButtons in Tab order Sequence (Command1, Command2, and Command3); it is suggested that you skip Command2:

         Private Sub Command1_LostFocus()
            Command3.SetFocus        'skip Command2
         End Sub
   
      NOTE: If Command1 opens a form, dialog, or other item that receives
      the focus, this will not work.
   
   

2. Add a dummy control, such as a CommandButton, and set its size to be very small to effectively hide it. (The Visible property must remain "True.") Set the TabIndex property to ensure it precedes the control to be skipped in the Tab order. Add code to its GotFocus event procedure to send the focus to desired control.

STATUS

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

MORE INFORMATION

Steps to Reproduce Behavior

1. Create a new Windows CE Project in Visual Basic 5.0. Form1 is created by default.

2. Add three CommandButtons to Form1.

3. Set the second CommandButton's TabStop property to False.

4. Press the F5 key to run the project.

   Pressing the TAB key will tab the focus from one button to the other, but the second CommandButton should not get the focus because its TabStop property is set to False.

REFERENCES

Online Books for Microsoft Windows CE Toolkit for Visual Basic version 5.0