>Geoff,
>
>In addition to Josh's recommendation to put a DoEvents in the loop. I'd suggest you get rid of that high processor use loop entirely.
>
>Just us a polling timer that checks every couple of seconds to see if the process is done. It may want to issue a DoEvents but it probably wouldn't be necessary.
>

David,

Josh was dead right, of course. My reply to him expaliains how I missed it.
I like the idea of a polling timer, but I am not sure how to implement it -
Does it mean something like this:
Start a timer in the ActivateEvent, so fire every second or so.
In its Timer Event, put what is currently the mainline code, using flags to determine whether an event is still in progress, or if finished, start the next process?
Maybry sort of did this, which was simpler, with a connect/send/disconnect and I went looking for a may to handle multiple sends in the middle..
Thank for your comments.

Geoff