From: harvestwind@comcast.net   
      
   Hi:   
      
   I have a procedure written in Visual Basic 4.0 that causes the window to   
   reduce in size and width until it is totally gone.  It sort of "melts" to   
   the lower right and then is gone.  The code is:   
      
   Sub ExitByClick   
      Dim I As Integer   
      Dim I As Long   
      
      I = Screen.TwipsPerPixelX   
      
      While Me.Height > 100   
         Me.Move Me.Left + I, Me.Top + I, Me.Width - (I * 5), Me.Height - (I *   
   5)   
      Wend   
      
      Unload Me   
   End Sub   
      
   It works fine in VB 4.0.   
      
   I put it in VB 5.0 and it is really messed up.  The form has a label on it   
   that seems to melt and then the form unloads... looks kinda lousy.  However,   
   if I put a lineunder the Me.Move statement (MsgBox "hi"), then it works   
   OK...except the message box pops up, I have to answer it and it pops again   
   and again and again until the form is gone. I watch the form behind the   
   message box and it is working correctly.   
      
   I've tried to "fool" it by putting a 'delay' in (a For Next Loop), but that   
   has no effect, but to slow the melting label down.   
      
   Does anyone know why this is happening in VB 5.0 and doesn't in 4.0 (the   
   language pertaining to the procedure is  the same in both)?  Is there a   
   "work around" that I might use?   
      
   Thanks for any assistance.   
      
   JP   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)