Anyone know a better way to suspend execution of VB code until an activex control responds and the event is handled other than using a loop with a doevents statement in it. Such a loop seems to be slowing my application significantly. Thanks.

I think this wouldn't really slow an app much. Windows’ "event-driven" interface is a continuously running loop. If your code is not looping, Windows is. Either way, there is repetitive looping taking place all the time.

It is possible that you have a loop that is designed in a way that is in fact slowing things, but the general idea doesn't seem to me to be necessarily a slowing way of doing things—I think...