From: mynamehere@comcast.net   
      
   "Max"  wrote in message   
   news:4598fc4c$0$5748$afc38c87@news.optusnet.com.au...   
   >   
   > This second timer is not firing while the long running process is taking   
   > place, the do events is working because the status of the long running   
   process   
   > is updated in the status bar of the application and that works.   
   >   
      
   I would bet that the second timer is firing with each DoEvents (unless you just   
   have the code mangled up).   
      
   It is more likely that it is is firing, but you are not seeing the out of   
   process component updated as you expect.   
      
   It should be easy to put in a visual queue that the second short timer is   
   indeed   
   firing during the long loop - a debug statement, a character added to a text   
   box   
   on a form, whatever works.   
      
   You might well find that the issue is more to do with the out of process   
   component not getting any processing time to update itself, since your app is   
   so   
   busy when it is in the long loop.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)