|
-
Dec 14th, 1999, 12:02 PM
#1
As far as I understand, the End command should never be used to end a program. It apparently leaves crap in memory. We are instead supposed to use Unload. If this is the case does the End command have another use or does MS refuse to remove a bad command?
-
Dec 14th, 1999, 12:28 PM
#2
Fanatic Member
Dear Nookta,
As long as I know about VB, the End command is just used to end your application.
No other use I think.
Just read your MSDN Help File, I'm sure it will help u a lot.
Regards,
Wille
-
Dec 14th, 1999, 03:45 PM
#3
Hyperactive Member
If you use the End command, the form_queryunload and form_unload events are not called (maybe some others too...) and since you usually clean up the mess you made in the form_unload, it's not so smart to use the end statement... I've seen some ppl using the end because the program didn't stop when they did Unload Me (or Unload FormName) but that indicates something is not going well in your app... I think End is available for backwards compatibility.. try not to use it...
-
Dec 14th, 1999, 06:53 PM
#4
Member
Yes, end usually means the programmer has a conflict and has not closed out properly.
Unload Form1
Set Form1 = Nothing
-
Dec 15th, 1999, 11:03 AM
#5
Lively Member
i think end should only be used when there is a need for immediate termination of the program. otherwise use unload to perform some clean-up tasks in the unload and terminate events.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|