This is a multi-part message in MIME format.

------=_NextPart_000_001C_01C21EC6.D5155C60
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Remove the END statement....

Quoting From MSDN....

The End statement stops code execution abruptly, without invoking the
Unload, QueryUnload, or Terminate event, or any other Visual Basic code.
Code you have placed in the Unload, QueryUnload, and Terminate events of
forms and class modules is not executed. Objects created from class modules
are destroyed, files opened using the Open statement are closed, and memory
used by your program is freed. Object references held by other programs are
invalidated.

The End statement provides a way to force your program to halt. For normal
termination of a Visual Basic program, you should unload all forms. Your
program closes as soon as there are no other programs holding references to
objects created from your public class modules and no code executing.




-----Original Message-----
From: Judy Henry [mailto:henryjud@n...]
Sent: Friday, June 28, 2002 4:58 PM
To: professional vb
Subject: [pro_vb] VB Program never ends


I have a VB program that as long as I run it in the VB6 environment runs and
quits with the END statement in the form_unload. I have compiled it to an
EXE file and when I run from there it still shows up in the task manager
after exiting the program.

I have check to see if there are any hidden forms, left over resources and
set them to nothing. Any help?