It looks as though it should work like you said. What goes wrong?

Got both responses.

Yikes! So the input routine is a general purpose string parser,
eh? I sort-of tried it, but only half-heartedly since I didn't think
it was valid. I don't think I actually tried the Parens "()"... just
did that for the posting. Better try again.
P.S.
In my half-hearted attempt to see if such a construct was possible,
I did get an error and therefore saw that Array is invalid for a
name...must be a key word. I changed to Arr() for my 'investigation'.

However, I am not actually doing that. The Array thing was only for
demo here and as a test vehicle for trying the construct. I did
rename starting at 0 for special reasons. I am putting the TextBox
value into a command string to send out the serial port. The
addresses into which the values go in the external device start at 0,
so subscripting is easier in the loop.

Worked like a charm. Didn't even have to convert the number to a
string. VB does that nicely for us.

This also helps me understand the collection construct.


My functional test routine:

[ x dim'ed elsewhere]
Text Boxes named DTMFName0 ... DTMFName9

Private Sub UserForm_Click()
For x = 0 To 9
Debug.Print x; " "; Controls("DTMFName" & x)
Next
End Sub

Array is not a legal name for a variable, I've used "Items". Also, you
don't need Me (it's implied because the code  is inside the user form's
module).

You need the Controls collection, which can be indexed by control name:

Items(X) = Controls("TextBox" & X)

Lastly, Excel starts numbering text  boxes and other controls from 1, not
from zero, so there won't be a TextBox0 unless you specifically call one
that.

Or you can use X as a simple subscript into the collection. In this case,
the subscripts do start at zero.

Items(X) = Controls(X)