This third version attempts to fix one problem in the second version. When you click on a button to start the loop running, you now get separate text boxes to display the results. This makes it easier to separate out the timing results for each variable type.

In each Click Event routine, I declared a static variable siNdex to keep track of how many times that button has been clicked. Since static variables retain their value for the life of the program, they can be used to identify how many times the Click event has occurred:

'Identify maximum number of columns we can show
Const fiMAX_COLS As Integer = 7

Private Sub cmdLong_Click()

Static siNdex As Integer
Dim liNdex As Integer

Dim llCounter1 As Long
Dim llCounter2 As Long
Dim llAccum As Long
Dim ldtStart As Date
Dim ldtStop As Date
Dim lsMsg As String

'Don't allow too many of these to run!
If siNdex > fiMAX_COLS - 1 Then Exit Sub

'Identify current loop number
liNdex = siNdex
siNdex = siNdex + 1

All the variables declared inside the cmdLong_Click event above (except for siNdex) will be re-initialized to zero each time the Click event is called. The reason is that the variables other than siNdex have local scope, and they are allocated dynamically on the stack each time the Click event occurs.

If you look in the properties window for the form object frmIntSpeed3, you'll see that each of the text boxes is defined as a control array. The item which makes them control arrays is having the Index property set to any value.

The final test in this If/Endif block is whether the new column of Text boxes extends beyond the right edge of the form.If so, we need to increase the Width property of the form. I used Me.Width, which refers to the current instance of the Form. This is the preferred method, instead of using frmIntSpeed3.Width.