>I've just been checking to see what happens, possibly the problem is due to the element not actually being deleted from the array.
>
>I don't think a 'memory leak' is going to be a problem, but eventually running out of memory might be. The added object is retained in the controls array of the form & the controlcount is not decremented when using your method of adding to an array, whereas when adding uniquely named objects, the object is removed from the control array & the countrol count decremented.
Well, I have used this for years now, and didn't seem to have serious trouble.
Anyway, I will have to check for memory leaks, and for methods of destroying individual items, and modify my FAQ correspondingly. If there turns out to be a memory leak, I will have to include a caveat, and alternative methods (as explained by Armin).
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
