Quote Originally Posted by reexre View Post
BTW: seems that "only controls that are created via Load can be deleted at runtime."
That was probably true for VB5 (where Controls.Add and Controls.Remove didn't exist).

With VB6 one can use both (the old Control-Array-based Load/Unload-mechanism, as well as the new introduced Controls.Add/Remove).

As said - the Controls.Remove-call is currently included in the little wrapper method: RemoveByLocalFileName

For your case (a "well-ordered retreat" in the "Form-TearDown-phase"), the cancelling of all still running async-download-jobs is probably enough
(no need to remove the "async-job-hosting" Stripe-Controls from their Host-Controls-Collection, since this is done anyways under the covers, when the Form finally closes).

Olaf