BUG: Corruption of TabIndex Property of Custom Controls

MORE INFORMATION

Steps to Reproduce Problem

1. Load Visual Basic for MS-DOS using this command line:

      VBDOS /L SPIN.QLB
   						

2. Create a form and add a control array of three spin controls in the lower-right corner of the form. Verify that the three controls have TabIndex and Index property values 0, 1, and 2 from left to right.
3. Add the following Sub procedure to the application:

      SUB Custom1_Custom (Index AS INTEGER, EventType AS INTEGER)
         FOR i = 0 TO 2
            PRINT Custom1(i).TabIndex;
         NEXT
         PRINT
      END SUB
   						

4. Run the application, and click any of the controls. The values printed should be 0 1 2, but instead appear as 0 2 1.
5. Exit the program and verify that the TabIndex property of each control in the control array is back to its original value.
6. Add three more spin controls to the form. Verify the TabIndex property of each control.
7. Replace the PRINT line of the Custom1_Custom Sub procedure with this:

      PRINT Custom2.TabIndex; Custom3.TabIndex; Custom4.TabIndex
   						

8. Run and click any of the first three controls. The values printed should be 0 1 2 3 4 5, but instead appear as 0 5 1 2 3 4.
9. Exit the program and verify that the TabIndex property of each control is back to its original value.

The TabIndex property of the second element of the control array is set to the last TabIndex on the form. All TabIndex properties greater than the original value of the TabIndex property of the second element in the control array are decreased by 1. It therefore becomes possible to work around this problem by setting all TabIndexes to the values they will assume when the program is run.