Thanks for that fellas

Actually the problem may be a little more involved.
Heres what happens exactly.

The combo box has a list of stored procedures (from an SQL Server 2000
database). When I select a stored procedure, I would like to show each
parameters name and value in a textbox (1 for name and 1 for value).
Each parameters name and value textbox forms a row (kind of) and for the
next parameter(s), I increment the Top property of the name and value
textbox so that the new controls sit below the previous ones. (do you
get that - they kind of look like a grid in the end)

If the stored procedure has 10 parameters, I would generate 10 rows (x 2
textboxes) giving a total of 20 textboxes.

However, if I've made the wrong selection in the combo and re-chose a
new stored procedure, I need to remove these 20 textboxes that I've
created (at runtime) and recreate a set of new textboxes which will
depend on the number of parameters that the newly selected stored
procedure contains. (possibly 0).

This is why i've created the sub ClearTemporaryControls which can be
called immediately after selecting the stored procedure but before the
new controls are created.

One thing you did say Tom was that you always deleted the zeroth indexed
control. Is this a rule when deleting controls at runtime or just good
practice. Also, if you do delete a control, is the index count
decremented also and do all controls after the deleted control have
their indexes decremented likewise?

*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!