SOLVED: Is simulated multithreading the way to go (for what i need to do)?

[evank]

First off, let me say I'm an experienced programmer, but I'm still reorienting myself with VB which I hadn't touched in some time.

I'm writing an app with a heavy-duty function call that takes about 5 minutes to complete (processing a list of files inside a loop). What happens is, the user clicks "Start" which triggers said function, and the program (predictably) becomes unresponsive until the function completes. What i'd like, however, is for the user to still be able to move the window or at least click a Cancel button if they need to abort it (the function itself is primarily a loop, so I could add a check at the end of said loop).

Now, I've read the horror stories about simulated multithreading in vb6, so I'm wondering...is there another (better) way?