Yeah, you're right, I should've specified a Text1(0) control on the form first.<br>
<br>
Sorry about the offtrack - I read that you wanted to add controls, not that you wanted to specifically use a collection for the purpose - my dumb.<br>
<br>
Problem with collections, at least in the 5.0 iteration of VB, is that they're pretty much either form or database related. You can work with an existing collection of controls, but you cannot create a _new_ collection of such(?!?). At least, that's what RTFM tells me.<br>
<br>
Theoretically, your statement ab. collections being a better option is correct, but in all practicality, that's not so much the case. First of all, the noted lack of creating the collection of choice comes to mind <grin!>. <br>
But, then, there is the not-so-obvious overhead trade-off to be considered. Which 'costs' more, the 'seed' control loading, or the creation time of the collection initialization? Can't speak to VB5 on this, but in VB3 and VB4, using a forms collection was always slow, so I quit doing it - but then, that could have been my implementation rather than any fault of the collections. (OK, begging the question for VB3, but VB4 had 'em <grin!>.)<br>
<br>
Getting back to that 'collection of choice' mentioned above, VB's limited capability in the collection area (i.e., creating new ones) is kinda frustrating (But you know that, no?), and pretty much self-flagellation when trying to step outside the limited examples (and instruction/advisory of the documentation). Since I'm pretty much restricted to the real (read 'practical'?) world, I've reverted to a proven, albeit older, technology.<br>
<br>
Yikes, I've gotten long-winded! Sorry! Also, sorry I couldn't help you to resolve your conundrum.<br>