I am fairly sure there is a DoEvents in there.  I would not have written   
   if there was not but, then again, sometimes I forget.   
      
   Thanks for the reminder, anyway.  I will check just to be sure.   
      
   Discussion will continue, if needed, on the DotNet forum.  Sorry for the   
   wrong post.   
      
   After a decade of VB6, jumping into the 3rd release of .NET is quite a   
   leap with no safety net (there might be one manual out by now -- due   
   Jan. 28th -- but most will appear in April).  My old 2003 .NET manual is   
   very lacking!   
      
   What fun...   
      
   Mike   
      
   On Fri, 1 Feb 2008 18:41:36 -0600, in comp.lang.visual.basic "Reverend   
   Fuzzy"  wrote:   
      
   >   
   >"Auric__"  wrote in message   
   >news:47a3aa68$0$26041$88260bb3@free.teranews.com...   
   >>> On 01 Feb 2008 19:50:50 GMT, in comp.lang.visual.basic "Auric__"   
   >>>  wrote:   
   >>>   
   >>>>On Fri, 01 Feb 2008 20:11:31 GMT,  wrote:   
   >>>>   
   >>>>> I tried me.close and application.exit.  Neither work.  Tried   
   >>>>> clicking the big red X and the form closed but the app kept   
   >>>>> running and producing debug.print output.   
   >>>>   
   >>>>Step through your app and find what's still running when the form   
   >>>>is closed. Implement a way to tell it to stop doing whatever it's   
   >>>>doing.   
   >>>>   
   >>>>> How does one definitely stop an app while in the IDE?  Well, one   
   >>>>> could click the blue stop button in the IDE but that usually   
   >>>>> leaves gobs of memory unaccounted for and will cause problems   
   >>>>> after a few reps as uncollected garbage memory clogs the program   
   >>>>> space.   
   >>>>>   
   >>>>> And starting and stopping this .NET beast is really slow!   
   >>>>   
   >>>>Try asking in a .net group.   
   >>   
   >> On Fri, 01 Feb 2008 23:48:47 GMT, "Just_a_fan" wrote:   
   >>   
   >>> Funny, when one runs application.exit, it seems the application   
   >>> should exit.  Thanks to the folks at M$, it does not.   
   >>   
   >> Yeah, you'd think so -- wait, I'm not a .net programmer! I don't know!   
   >>   
   >>> I found the dotnet groups.  Thanks for the pointer.  Will ask   
   >>> there.   
   >>   
   >> No prob. Glad you were able to find them without a specific pointer.   
   >>   
   >> --   
   >> ultimate_answer_t deep_thought(void) {   
   >>    sleep(years2secs(7500000));   
   >>    return 42;   
   >> }   
   >   
   >The problem here is not M$, it's the programmer...in this loop, you've   
   >left no way for the cpu to service other functions/subs. What you need   
   >is to increment a counter by firing a timer object.... then you can put   
   >something in to let the cpu do other things. (does .NET have a   
   >DoEvents function?)   
   >   
   >The way you've got it now, you're putting the whole system to sleep   
   >when it hits your loop... when will the cpu have time to see if you're   
   >pressing a stop button, or "x-ing out" of the application?  The program   
   >will never see the IDE again, until you've killed the process, IDE and all.   
   >   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)