Re: memory management in VB
Aggressively killing the object won't help, and I'm not so sure if unloading the Form is actually solving your problem, however,
you could try to multi-thread it(not in the true sense of the word) by launching another ActiveX EXE and have it create your object. At least your object "lives" in that Active EXE's process space, and you have the power to "agressively" kill that process.
Does anyone know if you've leaked memory...allocated memory in the heap(and didn't deallocate it)...does it deallocate that memory when the "parent" process is unloaded? My thought is that it doesn't. Once you've allocated it, its there to stay. If that's the case, then I don't think there's a way to manage your memory.
Sorry.