charlieosborne
asked on
Exiting a VB program
Can somebody help me with the coding needed for a button that will close a VB program I have created
reel
Just use the "End" statement. It will end the program.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Actually the End does do a better job than QueryUnload, queryunload only unloads the current form, end closes all open variables, and forms, it does not however terminate classes, this should be done by unload Class
XxDaKmanxX,
QueryUnload is a subroutine that is envoked when the form is exiting. You add in the code to set all forms, objects, classes to nothing there. Then you have no open "whatever" still in memory.
End leaves all that still open
QueryUnload is a subroutine that is envoked when the form is exiting. You add in the code to set all forms, objects, classes to nothing there. Then you have no open "whatever" still in memory.
End leaves all that still open
NEVER USE END.. The End.. <smile>.
Clicking the X will fire the Form_QueryUnload event. To achieve this elsewhwere in your code.. (like in a menu or command button procedure just simply put Unload Me in a statement. Here is a code example that a lot of developers use along with a sample cmdExit click event procedure:
<----- Code Begin ----->
Private Sub cmdExit_Click()
Unload Me
End Sub
Private Sub Form_QueryUnload(Cancel As Integer, UnloadMode As Integer)
Dim frmWork As Form
For Each frmWork In Forms
Unload frmWork
Set frmWork = Nothing
Next frmWork
End Sub
<----- Code End ----->
If in your Form_QueryUnload event.. you want to STOP program shutdown.. just do a Cancel = True and no shut down will take place. This is useful when an User has a file open, and you want to know whether he wants to save it before exiting. It is in the QueryUnload event procedure where they do that processing.
Clicking the X will fire the Form_QueryUnload event. To achieve this elsewhwere in your code.. (like in a menu or command button procedure just simply put Unload Me in a statement. Here is a code example that a lot of developers use along with a sample cmdExit click event procedure:
<----- Code Begin ----->
Private Sub cmdExit_Click()
Unload Me
End Sub
Private Sub Form_QueryUnload(Cancel As Integer, UnloadMode As Integer)
Dim frmWork As Form
For Each frmWork In Forms
Unload frmWork
Set frmWork = Nothing
Next frmWork
End Sub
<----- Code End ----->
If in your Form_QueryUnload event.. you want to STOP program shutdown.. just do a Cancel = True and no shut down will take place. This is useful when an User has a file open, and you want to know whether he wants to save it before exiting. It is in the QueryUnload event procedure where they do that processing.
>Actually the End does do a better job than QueryUnload, queryunload only
>unloads the current form, end closes all open variables, and forms, it does not
>however terminate classes, this should be done by unload Class
QueryUnload does not unload the form. The Unload statement does that. Some examples:
Unload Me
Unload Form1
The QueryUnload routine is called AS A RESULT OF the form unloading; *not* as a means to unload the form.
Furthermore, you should *NEVER* use the End statement. The End Statement causes your program to terminate ABNORMALLY. This is not good. See the VB Help file for more information about the End statement.
The End statement ABRUBTLY and IMMEDIATELY terminates your program, *without* invoking any of the QueryUnload events, Unload Events, Terminate Events, etc.
This can cause severe problems, especially when you have hooks in place (subclassing, etc), or when you are using ActiveX controls and Class Modules. Or if you have any files open, such as databases. All these things do not get closed properly and nicely when you use the End statement.
Using the End statement is like quickly putting your car into Park while driving 60mph down the interstate. Will you get stopped. Sure; but you will have problems, such as transmission parts strewn all over the road.
To allow your program to terminate NORMALLY, simply unload all forms, make sure no code is running, unhook any hooks you might have in place, and release all object references you have in place.
Then you program will terminate normally. :-)
-Dennis Borg
President PAUES
>unloads the current form, end closes all open variables, and forms, it does not
>however terminate classes, this should be done by unload Class
QueryUnload does not unload the form. The Unload statement does that. Some examples:
Unload Me
Unload Form1
The QueryUnload routine is called AS A RESULT OF the form unloading; *not* as a means to unload the form.
Furthermore, you should *NEVER* use the End statement. The End Statement causes your program to terminate ABNORMALLY. This is not good. See the VB Help file for more information about the End statement.
The End statement ABRUBTLY and IMMEDIATELY terminates your program, *without* invoking any of the QueryUnload events, Unload Events, Terminate Events, etc.
This can cause severe problems, especially when you have hooks in place (subclassing, etc), or when you are using ActiveX controls and Class Modules. Or if you have any files open, such as databases. All these things do not get closed properly and nicely when you use the End statement.
Using the End statement is like quickly putting your car into Park while driving 60mph down the interstate. Will you get stopped. Sure; but you will have problems, such as transmission parts strewn all over the road.
To allow your program to terminate NORMALLY, simply unload all forms, make sure no code is running, unhook any hooks you might have in place, and release all object references you have in place.
Then you program will terminate normally. :-)
-Dennis Borg
President PAUES
hes:
Gawd.. its bad enough putting with all the memory leaks that Microsoft gives us.. just imagine what are System Resources would be like after running a XxDaKmanxX and/or reel application?.. LOL. No offense intended XxDaKmanxX and reel.. <smile>.
When VB comes across an End statement.. it immediately just completely stops processing. It doesn't close Files.. It doesn't unload Components.. It doesn't Dereference objects.. It doesn't clean up memory.. the program just pulls up stakes often leaving a mess behind it. Fortunately.. there is a way to clean up the mess.. at the blue screen of death.. (that eventually will appear if you do this over and over).. just reboot the computer!
The code I provided above.. is the way MOST developers shut down their programs. If when they hit Exit, the program does NOT finish.. then that means there still is a reference open to something somewhere.. and they immediately go find it and correct it. It is only common courtesy and good programming practice.. to leave a machine as clean as you leave, as when you first started.. <smile>.
Gawd.. its bad enough putting with all the memory leaks that Microsoft gives us.. just imagine what are System Resources would be like after running a XxDaKmanxX and/or reel application?.. LOL. No offense intended XxDaKmanxX and reel.. <smile>.
When VB comes across an End statement.. it immediately just completely stops processing. It doesn't close Files.. It doesn't unload Components.. It doesn't Dereference objects.. It doesn't clean up memory.. the program just pulls up stakes often leaving a mess behind it. Fortunately.. there is a way to clean up the mess.. at the blue screen of death.. (that eventually will appear if you do this over and over).. just reboot the computer!
The code I provided above.. is the way MOST developers shut down their programs. If when they hit Exit, the program does NOT finish.. then that means there still is a reference open to something somewhere.. and they immediately go find it and correct it. It is only common courtesy and good programming practice.. to leave a machine as clean as you leave, as when you first started.. <smile>.
<offthread>
DennisBorg:
Gawd.. YOU are getting almost as fast at typing as azrasound <lol>, as I keyed my little lecture at the same time you did yours.. <smile>.
By the way.. Hear!!! Hear!!!.. For an excellent comment by YOU .. <smile>.
DennisBorg:
Gawd.. YOU are getting almost as fast at typing as azrasound <lol>, as I keyed my little lecture at the same time you did yours.. <smile>.
By the way.. Hear!!! Hear!!!.. For an excellent comment by YOU .. <smile>.
wsh2:
>Gawd.. YOU are getting almost as fast at typing as azrasound <lol>, as I keyed my little lecture at the same time you did yours..
:-) Have to type faster! ... "self-defense" ... otherwise too many other people get the right answer in before mine. They'd post a short answer before I was done composing mine. Sometimes, the questioner even selected an answer while I was composing my post. LOL!
I've been noticing a few more mistakes, however. For example "Then you program will ..." instead of "Then *your* program will ..." :-)
>By the way.. Hear!!! Hear!!!.. For an excellent comment by YOU .. <smile>.
Thank you!
-Dennis Borg
>Gawd.. YOU are getting almost as fast at typing as azrasound <lol>, as I keyed my little lecture at the same time you did yours..
:-) Have to type faster! ... "self-defense" ... otherwise too many other people get the right answer in before mine. They'd post a short answer before I was done composing mine. Sometimes, the questioner even selected an answer while I was composing my post. LOL!
I've been noticing a few more mistakes, however. For example "Then you program will ..." instead of "Then *your* program will ..." :-)
>By the way.. Hear!!! Hear!!!.. For an excellent comment by YOU .. <smile>.
Thank you!
-Dennis Borg
wsh2
<<hes:
Gawd.. its bad enough putting with all the memory leaks that Microsoft gives us.. just imagine what are System Resources would be like after running a XxDaKmanxX and/or reel application?.. LOL. No offense intended XxDaKmanxX and reel.. <smile>. >>
Been there done that, user calls my program can't be run anymore not enough memory, gee guess what there are a few hundred instances of another vb program still lingering around (not mine :) )
Answer sorry contact the other programmer to fix his code LOL
<<hes:
Gawd.. its bad enough putting with all the memory leaks that Microsoft gives us.. just imagine what are System Resources would be like after running a XxDaKmanxX and/or reel application?.. LOL. No offense intended XxDaKmanxX and reel.. <smile>. >>
Been there done that, user calls my program can't be run anymore not enough memory, gee guess what there are a few hundred instances of another vb program still lingering around (not mine :) )
Answer sorry contact the other programmer to fix his code LOL
Dennis,
May I copy you in a few other places with your comment of :
Using the End statement is like quickly putting your car into Park while driving 60mph down the interstate. Will you get stopped. Sure; but you will have problems, such as transmission parts strewn all over the road.
Love it LOL
May I copy you in a few other places with your comment of :
Using the End statement is like quickly putting your car into Park while driving 60mph down the interstate. Will you get stopped. Sure; but you will have problems, such as transmission parts strewn all over the road.
Love it LOL
Hes:
>Dennis,
?May I copy you in a few other places with your comment of :
>
>Using the End statement is like quickly putting your car into Park while driving
>60mph down the interstate. Will you get stopped. Sure; but you will have
>problems, such as transmission parts strewn all over the road.
Sure, go ahead. :-)
-Dennis Borg
>Dennis,
?May I copy you in a few other places with your comment of :
>
>Using the End statement is like quickly putting your car into Park while driving
>60mph down the interstate. Will you get stopped. Sure; but you will have
>problems, such as transmission parts strewn all over the road.
Sure, go ahead. :-)
-Dennis Borg
charlieosborne:
Where are you at on this question? Wsh2 has the answer you're looking for.
-Dennis Borg
Where are you at on this question? Wsh2 has the answer you're looking for.
-Dennis Borg
That is not true about the End commmand. I hate when people who dont know too much about programming talk like the Masters of the Art. It gives all of us a bad name. I have been programming for many years and always use the END command.
BTW: All you people should always press F1, in VB, for any questions you may have. If you do and look up the word "END" it says, and I quote "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 offorms andclass 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."
Read the last couple lines, "memory used by your programs is freed...".
Dont believe the hype guys.
Happy Coding
BTW: All you people should always press F1, in VB, for any questions you may have. If you do and look up the word "END" it says, and I quote "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 offorms andclass 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."
Read the last couple lines, "memory used by your programs is freed...".
Dont believe the hype guys.
Happy Coding
Paul__420:
ROFLMAO.. and elephants can fly, right?
ROFLMAO.. and elephants can fly, right?
Do you think I made all that up??
No.. I'm sure your "Hello World" program works GREAT!.. <smile>.
How about an ERP system for over 2,000 users?? with Oracle back-end?? rook
Paul__420:
>That is not true about the End commmand. I hate when people who
>dont know too much about programming talk like the Masters of the
>Art. It gives all of us a bad name. I have been programming for many years
>and always use the END command.
What I have said about the End statement is most certainly true. I hate it when people *THINK* they know what they're talking about, and they simply do not!!! Talk about giving us a bad name!!!
>BTW: All you people should always press F1, in VB, for any questions you may have. If you do and look up the
>word "END" it says, and I quote "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 offorms andclass 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."
You should also take your own advice, only this time, read the documentation more *carefully*, and *completely*!
Notice the words used in describing the manner of which the End statement terminates your program:
**************************
Abruptly
**************************
This doesn't sound good!! "Abruptly" has a negative connotation, and was used in the documentation for a reason.
Notice that words such as "immediately", "quickly", or "expediently" were *not* used. These would mean essentially the same thing, except they indicate something positive.
I sure do not want my applications to end "Abruptly"!!
**************************
without invoking the Unload, QueryUnload, or Terminate event, or any other Visual Basic code.
**************************
Are you telling us, Paul, that all the code in the QueryUnload, Unload, and Terminate event procedures are not important?! That is interesting, especially since the QueryUnload event is new; it was just added in either VB 5 or 6. Why add them if they're not important?!
What kind of work is usually performed from those procedures? Do you know?!
Well, they are used, among other things, to close files and databases, to unset hooks which have been set (keyboard/mouse hooks, WinProc hooks [subclassing], call-back function hooks, etc). They are used to free up object references which BTW, causes those object's Terminate event to be triggered. This means that if you have any class modules in your project, and you just abruptly end your program, your class modules' Terminate event is never invoked.
I suppose the code in those events are not important.
Since the Unload, QueryUnload, and Terminate events are never invoked, any code you have to unset any hooks you have in place does not need to be executed. And code which is supposed to handle call-back routines can simply disappear; and when your program crashes, and the others which you are subclassing as well, the GPF's you get are not important!
>Read the last couple lines, "memory used by your programs is freed...".
You think that memory is the only issue here?!
As I mentioned earlier, you should take your own advice, and read the VB documentation, only more carefully and completely this time. What you quoted as the last couple lines are *NOT*, in fact, the last couple lines.
You missed the next paragraph completely. And I quote:
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.
**************************
End statement - a way to FORCE your program to halt
**************************
More negative connotation. Why would I need to "FORCE" my program to halt?! Probably because I am not doing something right. Or the OS has become unstable. Or some other similiar situation. Yes, I would want to FORCE my program to halt if there were some serious problem happening!!!
But it is *never preferable* to FORCE your program to halt. Especially when you can experience a *normal termination*!!
**************************
For normal termination of a Visual Basic program, you should unload all forms ... ... ...
**************************
For "NORMAL TERMINATION", as compared to what?! Abnormal, abrupt termination that does not invoke your Unload, QueryUnload, and Terminate Events?! Hmmmm.......
Normal Termination sure sounds more favorable to me!! Besides, I like it when my applications have a chance to close files, close databases, unset hooks I've set, etc, etc., etc.
I've seen many people post questions along the lines of:
"When I close my program, it crashes! How can I fix it?!"
Later, you find the following:
"It is fine, until it gets to the End statement"
Ahhhhaaaa!!! Eureka!!! Funny how when they stop using the End statement, and try for the normal termination, the GPF's suddenly "dissappear"!!!
Memory leaks? Yes, they can also happen. I seem to recall a problem that Microsoft had with VB3, where the memory for some objects were not freed up, and the solution was to, ..... can you guess? ..... yes! it was actually recommended that you set the object to nothing! Simply amazing, isn't it?!
The Microsoft name or logo on a product does not guarantee a bug-free product!
Your apparent concept of leaving your application in a state of disarray, and leaving it up to the operating system to clean up after your program is disconcerting. Just thow in an End statement, Windows will close out everything for you!
I would call that sloppy programming!
I suppose you also shut down your computer simply by pulling the plug. After all, your files and databases will no longer be open. Your memory will be cleared and ready for when you restart your system. Write-behind disk caching (which I never use, BTW), .... oh, well! You don't need that ShutDown option on the Start Menu!
I apologize for the sarastic tone in my post. But as someone else once said:
"I hate when people who dont know
too much about programming talk
like the Masters of the Art. It gives
all of us a bad name."
So, Paul, go ahead and use the End statement. But I would not want to run any of your programs on my system!
-Dennis Borg
>That is not true about the End commmand. I hate when people who
>dont know too much about programming talk like the Masters of the
>Art. It gives all of us a bad name. I have been programming for many years
>and always use the END command.
What I have said about the End statement is most certainly true. I hate it when people *THINK* they know what they're talking about, and they simply do not!!! Talk about giving us a bad name!!!
>BTW: All you people should always press F1, in VB, for any questions you may have. If you do and look up the
>word "END" it says, and I quote "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 offorms andclass 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."
You should also take your own advice, only this time, read the documentation more *carefully*, and *completely*!
Notice the words used in describing the manner of which the End statement terminates your program:
**************************
Abruptly
**************************
This doesn't sound good!! "Abruptly" has a negative connotation, and was used in the documentation for a reason.
Notice that words such as "immediately", "quickly", or "expediently" were *not* used. These would mean essentially the same thing, except they indicate something positive.
I sure do not want my applications to end "Abruptly"!!
**************************
without invoking the Unload, QueryUnload, or Terminate event, or any other Visual Basic code.
**************************
Are you telling us, Paul, that all the code in the QueryUnload, Unload, and Terminate event procedures are not important?! That is interesting, especially since the QueryUnload event is new; it was just added in either VB 5 or 6. Why add them if they're not important?!
What kind of work is usually performed from those procedures? Do you know?!
Well, they are used, among other things, to close files and databases, to unset hooks which have been set (keyboard/mouse hooks, WinProc hooks [subclassing], call-back function hooks, etc). They are used to free up object references which BTW, causes those object's Terminate event to be triggered. This means that if you have any class modules in your project, and you just abruptly end your program, your class modules' Terminate event is never invoked.
I suppose the code in those events are not important.
Since the Unload, QueryUnload, and Terminate events are never invoked, any code you have to unset any hooks you have in place does not need to be executed. And code which is supposed to handle call-back routines can simply disappear; and when your program crashes, and the others which you are subclassing as well, the GPF's you get are not important!
>Read the last couple lines, "memory used by your programs is freed...".
You think that memory is the only issue here?!
As I mentioned earlier, you should take your own advice, and read the VB documentation, only more carefully and completely this time. What you quoted as the last couple lines are *NOT*, in fact, the last couple lines.
You missed the next paragraph completely. And I quote:
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.
**************************
End statement - a way to FORCE your program to halt
**************************
More negative connotation. Why would I need to "FORCE" my program to halt?! Probably because I am not doing something right. Or the OS has become unstable. Or some other similiar situation. Yes, I would want to FORCE my program to halt if there were some serious problem happening!!!
But it is *never preferable* to FORCE your program to halt. Especially when you can experience a *normal termination*!!
**************************
For normal termination of a Visual Basic program, you should unload all forms ... ... ...
**************************
For "NORMAL TERMINATION", as compared to what?! Abnormal, abrupt termination that does not invoke your Unload, QueryUnload, and Terminate Events?! Hmmmm.......
Normal Termination sure sounds more favorable to me!! Besides, I like it when my applications have a chance to close files, close databases, unset hooks I've set, etc, etc., etc.
I've seen many people post questions along the lines of:
"When I close my program, it crashes! How can I fix it?!"
Later, you find the following:
"It is fine, until it gets to the End statement"
Ahhhhaaaa!!! Eureka!!! Funny how when they stop using the End statement, and try for the normal termination, the GPF's suddenly "dissappear"!!!
Memory leaks? Yes, they can also happen. I seem to recall a problem that Microsoft had with VB3, where the memory for some objects were not freed up, and the solution was to, ..... can you guess? ..... yes! it was actually recommended that you set the object to nothing! Simply amazing, isn't it?!
The Microsoft name or logo on a product does not guarantee a bug-free product!
Your apparent concept of leaving your application in a state of disarray, and leaving it up to the operating system to clean up after your program is disconcerting. Just thow in an End statement, Windows will close out everything for you!
I would call that sloppy programming!
I suppose you also shut down your computer simply by pulling the plug. After all, your files and databases will no longer be open. Your memory will be cleared and ready for when you restart your system. Write-behind disk caching (which I never use, BTW), .... oh, well! You don't need that ShutDown option on the Start Menu!
I apologize for the sarastic tone in my post. But as someone else once said:
"I hate when people who dont know
too much about programming talk
like the Masters of the Art. It gives
all of us a bad name."
So, Paul, go ahead and use the End statement. But I would not want to run any of your programs on my system!
-Dennis Borg
You guys are funny.
The point is MAYBE I NEED TO END ABRUPTLY. Most the time you would use the events listed, duh! Also each of those events the programmer is able to edit, meaning that, the programmer obviously knows what is going on in all those events. A programmer might want to use the END command in the Unload event. Gosh you guys are stupid, no wonder I get paid the big bucks.
The point is MAYBE I NEED TO END ABRUPTLY. Most the time you would use the events listed, duh! Also each of those events the programmer is able to edit, meaning that, the programmer obviously knows what is going on in all those events. A programmer might want to use the END command in the Unload event. Gosh you guys are stupid, no wonder I get paid the big bucks.
>You guys are funny.
No more funny than are you!
>The point is MAYBE I NEED TO END ABRUPTLY. Most the time you would use the events listed, duh!
Oh! **NOW** he sees the need for those events!
*WHEN* would you *NEED* to end *abruptly*? Please, enlighten us, O Great One!
Perhaps when your appliction is already crashing and burning, and because of this, your program cannot terminate *normally*? Perhaps, for some reason, Windows has become very unstable and because of this, your program cannot terminate normally. I can see *that* as a valid reason!
>Also each of those events the programmer is able to edit, meaning
>that, the programmer obviously knows what is going on in all those events.
So?!! Just because one knows what is going on in the various events in his/her own program, does not make the use of the End statement a wise, nor a safe, choice.
>A programmer might want to use the END command in the Unload event.
Why?!! What does that do for you? It is quite obvious that, since you are already in the Unload event, the form is *already* closing.
Still, that does not mean that you want your program to end.
Oh, so only put the END statement in the Unload event of your *MAIN* form!! I get it!!!
But, wait!! What about the Unload event of all the other loaded forms in your project?!!!! Remember, the Unload and QueryUnload events are not going to be executed for those form objects either!!!!
And what about the object references you have in place? Your class modules? Your custom controls? The Terminate Event for your objects in your project won't get called. Remember, the Terminate Event procedure is not invoked when you use the End statement (the ABRUPT ENDING, remember?!)
Oh! I know!!! Use the End statement *only* in your *MAIN FORM*, and use a loop prior to the End statement to unload all your forms.
Oh! Oh! Oh! :::jumping up and down on my chair::: You can even free up all object references BEFORE invoking the End statement. This way, your Terminate events for your own classes are triggered!!! COOOOOOLLLLL!!!!
You could also close all your files and databases, unset any hooks and callback functions you have in place, etc. *before* invoking the End statement!!! This is SOOOOO cool!
::drool dripping from the corners of my mouth::
You just taught me SOOOOOOOOO much!!!! Thank you, oh wise-guy, er... Wise One.
But, I have just one more question. Since you've already done everything required to *gracefully* bring your application to a *normal termination*, WHY use the End statement? The program is *ALREADY* prepared to quit very nicely without it!!!
Answer:
YOU DON'T NEED TO USE THE END STATEMENT!!!!!
>Gosh you guys are stupid, no wonder I get paid the big bucks.
"stupid"?! ::::picking myself up from off the floor::::
"big bucks"?! ::::picking myself up from off the floor::::
(Boy, that floor sure is hard!!)
I'm sorry, Paul. If choosing to bring my programs safely and gracefully to a Normal Termination is "stupid"; and abnormally ending my programs abruptly is "wise", then I'd rather be stupid than to have your so-called "wisdom".
-Dennis Borg
No more funny than are you!
>The point is MAYBE I NEED TO END ABRUPTLY. Most the time you would use the events listed, duh!
Oh! **NOW** he sees the need for those events!
*WHEN* would you *NEED* to end *abruptly*? Please, enlighten us, O Great One!
Perhaps when your appliction is already crashing and burning, and because of this, your program cannot terminate *normally*? Perhaps, for some reason, Windows has become very unstable and because of this, your program cannot terminate normally. I can see *that* as a valid reason!
>Also each of those events the programmer is able to edit, meaning
>that, the programmer obviously knows what is going on in all those events.
So?!! Just because one knows what is going on in the various events in his/her own program, does not make the use of the End statement a wise, nor a safe, choice.
>A programmer might want to use the END command in the Unload event.
Why?!! What does that do for you? It is quite obvious that, since you are already in the Unload event, the form is *already* closing.
Still, that does not mean that you want your program to end.
Oh, so only put the END statement in the Unload event of your *MAIN* form!! I get it!!!
But, wait!! What about the Unload event of all the other loaded forms in your project?!!!! Remember, the Unload and QueryUnload events are not going to be executed for those form objects either!!!!
And what about the object references you have in place? Your class modules? Your custom controls? The Terminate Event for your objects in your project won't get called. Remember, the Terminate Event procedure is not invoked when you use the End statement (the ABRUPT ENDING, remember?!)
Oh! I know!!! Use the End statement *only* in your *MAIN FORM*, and use a loop prior to the End statement to unload all your forms.
Oh! Oh! Oh! :::jumping up and down on my chair::: You can even free up all object references BEFORE invoking the End statement. This way, your Terminate events for your own classes are triggered!!! COOOOOOLLLLL!!!!
You could also close all your files and databases, unset any hooks and callback functions you have in place, etc. *before* invoking the End statement!!! This is SOOOOO cool!
::drool dripping from the corners of my mouth::
You just taught me SOOOOOOOOO much!!!! Thank you, oh wise-guy, er... Wise One.
But, I have just one more question. Since you've already done everything required to *gracefully* bring your application to a *normal termination*, WHY use the End statement? The program is *ALREADY* prepared to quit very nicely without it!!!
Answer:
YOU DON'T NEED TO USE THE END STATEMENT!!!!!
>Gosh you guys are stupid, no wonder I get paid the big bucks.
"stupid"?! ::::picking myself up from off the floor::::
"big bucks"?! ::::picking myself up from off the floor::::
(Boy, that floor sure is hard!!)
I'm sorry, Paul. If choosing to bring my programs safely and gracefully to a Normal Termination is "stupid"; and abnormally ending my programs abruptly is "wise", then I'd rather be stupid than to have your so-called "wisdom".
-Dennis Borg
>Gosh you guys are stupid, no wonder I get paid the big bucks.
BTW, Paul. Are you, in some way, trying to imply that I don't get paid well? Or that you know how much I make?
Also, I'm still curious. Do you typically shut down your system by ABRUPTLY hitting the power switch? (instead of using the Shutdown option on the Start Menu)
I just love your professionalism in calling all of us "stupid", which is precisely why I am using this tone in my responses to your (infinitely wise) comments.
-Dennis Borg
BTW, Paul. Are you, in some way, trying to imply that I don't get paid well? Or that you know how much I make?
Also, I'm still curious. Do you typically shut down your system by ABRUPTLY hitting the power switch? (instead of using the Shutdown option on the Start Menu)
I just love your professionalism in calling all of us "stupid", which is precisely why I am using this tone in my responses to your (infinitely wise) comments.
-Dennis Borg
Looking at paycheck...... Wondering how Paul knows the size of it.
:::trembling::: I hope I don't loose my job to Paul!!!
Maybe I'll get a big raise, just for using the End statement!!
-Dennis Borg
Maybe I'll get a big raise, just for using the End statement!!
-Dennis Borg
lol, I can also till you a million times not to use the END command. OK Im sorry guys, I guess Im just not as good as guys. In any of the zillion languages I know, lol.
Oh that should have been tell not till, rookies
And Dennis you wont lose your job to me, You will just be programming in my language.
". 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" again direct from Microsoft, What else do you worry about?? lol.
Careful DennisBorg.. this guy DOES make BIG BUCKS.. All grocery baggers are the ERP checkout counter are very well paid!!
"Now.. would you like paper or plastic?"
Clearly Paul__420 could be working in a higher postion.. but he would always bail out when swiping the ERP customer's credit card.. "Now Paul.. it is forward AND THEN BACK".. as binary things are very confusing to he and he could never paint a very pretty image for anyone to see.
All I can say is I'm glad I'm not a woman.. can you imagine this guy in bed?.. In being a bagboy, you would think the words "Thank YOU Ma'am and please come again" would be ingrained in his head.. but orderly shutdowns are just not his strength.. maybe some day.. he will learn.. <smile>.
Still everyone has their own style. Old Experts like DennisBorg and I.. do kinda program in an old fashioned way. When we want to unload our programs.. we put in a Quit command button or Exit menu item or just tell the user to hit the X in the upper right corner. Heck, to be honest, we never even thought of the NEW AND IMPROVED Paul__420 way for program termination.. a shortcut key!!!.. Gotta hand it to ya Paul_420.. pressing Alt-Ctrl-Del twice to END any/all of your programs is a most novel idea.. and Wow.. do you ever get a clean machine after that sucker reboots! Face it Paul__420.. you ARE a GENIUS!!!
<rut roh>.. I just heard the PA system go off.. "Paul__420, Cleanup aisle 9".. <sigh>.. aren't those Computer Operations people a b*tch!!!.. <LOL> and a <smile>.
"Now.. would you like paper or plastic?"
Clearly Paul__420 could be working in a higher postion.. but he would always bail out when swiping the ERP customer's credit card.. "Now Paul.. it is forward AND THEN BACK".. as binary things are very confusing to he and he could never paint a very pretty image for anyone to see.
All I can say is I'm glad I'm not a woman.. can you imagine this guy in bed?.. In being a bagboy, you would think the words "Thank YOU Ma'am and please come again" would be ingrained in his head.. but orderly shutdowns are just not his strength.. maybe some day.. he will learn.. <smile>.
Still everyone has their own style. Old Experts like DennisBorg and I.. do kinda program in an old fashioned way. When we want to unload our programs.. we put in a Quit command button or Exit menu item or just tell the user to hit the X in the upper right corner. Heck, to be honest, we never even thought of the NEW AND IMPROVED Paul__420 way for program termination.. a shortcut key!!!.. Gotta hand it to ya Paul_420.. pressing Alt-Ctrl-Del twice to END any/all of your programs is a most novel idea.. and Wow.. do you ever get a clean machine after that sucker reboots! Face it Paul__420.. you ARE a GENIUS!!!
<rut roh>.. I just heard the PA system go off.. "Paul__420, Cleanup aisle 9".. <sigh>.. aren't those Computer Operations people a b*tch!!!.. <LOL> and a <smile>.
lol
And what language would that be Paul ?
rookies LOL
rookies LOL
The reason you guys only get 50k a year, is because you guys are here all day, typing long ass messages. Try practicing some coding.
I havn't earned that little in years
Paul:
Please be sure to read all of this, Paul, as it has some more information for you DIRECT FROM MICROSOFT.
>In any of the zillion languages I know, lol.
And *what*, pray tell, does knowing other languages have to do with how the VB End statement works? Or with *how* it should or should not be used? Does it work one way if you know only 1 or 2 languages? But work another way if you know, say, a zillion languages?
You'd have thought that in your learning of a zillion languages (and I'm am quite [un]impressed, ya know), that you would have learned a few good programming habits and the fundamentals of good application design.
>And Dennis you wont lose your job to me, You will just be programming in my language.
Good. Because I was SOOO very worried about it!! NOT!! ROFLMAOCFOOMP!!!
BTW, what language is "your" language? 'cuz I sure want to stay away from it!!!
(Does it sport an END statement?!!)
>". Objects created from class modules are destroyed,
Just be sure not to put any code into your class modules' Terminate Event!!! 'Cuz it ain't ever gonna be executed!!
Now what in the world is the purpose of the Terminate Event again?!!!
>files opened using the Open statement are closed, and memory used by your
>program is freed. Object references held by other programs are invalidated"
>again direct from Microsoft,
Microsoft is describing how to FORCE your application into an ABNORMAL TERMINATION.
Again, the VERY NEXT PARAGRAPH describes how to achieve a NORMAL TERMINATION.
So, your quote hardly shows Microsoft as endorsing the use of the End statement as the desired means of shutting down your program!
>What else do you worry about?? lol.
Well, let's see. There are call-back functions and subclassed processes, among other things.
Paul, just try implementing out-of-process subclassing, and abruptly end your program without replacing your Windows Procedure. You'll crash not only YOUR program, but the other program as well!
For that matter, try implementing in-process subclassing and abruptly end your program without replacing your Windows Procedure. Again, your program will crash and burn, EVERY TIME!
Now THAT is just *brilliant*!!
Besides, I much prefer Normal Termination instead of Brute-Forced, Abnormal Termination that circumvents all my code in the QueryUnload, Unload, and Terminate Event Procedures!!
Since you put so much emphasis on "DIRECT FROM MICROSOFT", (even though you completely ignore the following paragraph on achieving *normal termination*), here's another quote from Direct From Microsoft:
---MS KB Article Q129885-------------------
The End statement is convient, but it does NOT go through the complete sequence of cleaning up after your application. You should use it cautiously and sparingly when developing applications
--------------------------
FYI, Paul. "cautiously and sparingly" does not imply "all the time, and perhaps only in the Unload event of your form".
This KB Article (Direct from Microsoft), discusses a problem of an OLE Server with loaded forms not unloading when the client program (like one of yours, Paul), terminates by using the (beloved) End statement, even if the OLE server is programmed to unload its forms in the Terminate Event.
So here is how one of YOUR programs can cause grief for SOMEONE ELSE'S program, even though they did everything right.
All because YOU decided to use the END statement!
More info, DIRECT FROM MICROSOFT:
--------------------------
A Visual Basic client can destroy the last instance of an OLE Server it creates by:
- Setting it to Nothing (the preferred method)
- Shutting down by unloading the last form (acceptable, but not as desirable)
- Ending the probram by executing the End statement (this can cause problems)
--------------------------
Hmmm..... End statement not even acceptable. .... could cause problems.
But what the h--- does Microsoft know?!!!
Who do I believe, Microsoft (who created the product), or Paul__420? Microsoft .... Paul .... hmmmmm .... tough choice!
Paul, I fear that I have just turned you against Microsoft. For even they go contrary to your infinite wisdom in the use of the End statement.
But then again, this must be all hype!
Again, as to using the End statement in your Unload Event Procedure. If you're going to unload all your own forms, close all your files, unhook all hooks, etc, etc., etc., then you don't need the End statement, because your program is going to terminate anyway (NORMALLY). (No need to kick someone out the door when they are already leaving!)
>lol, I can also till you a million times not to use the END command. OK Im
>sorry guys, I guess Im just not as good as guys.
Look, I'm not trying to convice *YOU*. For you cannot push a wet noodle anywhere.
But I *can*, perhaps, prevent some beginners from falling into the pit falls you'd lead them into.
>... is because you guys are here all day, typing long ass messages. Try practicing some coding.
I get my job done early, and I do it right. That way, I don't have to waste my time debugging my programs from problems caused by using the End statement. <grin>
That gives me spare time to type these long-ass messages!
"zillions of languages" ... "rookie" ... You sound like a kid looking for an ego boost, trying to impress everyone with your (alleged) vast wealth and expertise.
::stroke:: ::stroke:: There, now does your ego feel better?
I get paid well, especially in my private practice. And I know more than one programming language. Yet I don't brag about it, nor do I proclaim my claim to fame.
Grow up and get a life!
-Dennis Borg
P.S. You can have the KB Article Q129885 e-mailed to you by sending an e-mail addressed to mshelp@microsoft.com, with Q129885 as the subject.
Or, read it here at:
http://support.microsoft.com/support/kb/articles/Q129/8/85.asp
Please be sure to read all of this, Paul, as it has some more information for you DIRECT FROM MICROSOFT.
>In any of the zillion languages I know, lol.
And *what*, pray tell, does knowing other languages have to do with how the VB End statement works? Or with *how* it should or should not be used? Does it work one way if you know only 1 or 2 languages? But work another way if you know, say, a zillion languages?
You'd have thought that in your learning of a zillion languages (and I'm am quite [un]impressed, ya know), that you would have learned a few good programming habits and the fundamentals of good application design.
>And Dennis you wont lose your job to me, You will just be programming in my language.
Good. Because I was SOOO very worried about it!! NOT!! ROFLMAOCFOOMP!!!
BTW, what language is "your" language? 'cuz I sure want to stay away from it!!!
(Does it sport an END statement?!!)
>". Objects created from class modules are destroyed,
Just be sure not to put any code into your class modules' Terminate Event!!! 'Cuz it ain't ever gonna be executed!!
Now what in the world is the purpose of the Terminate Event again?!!!
>files opened using the Open statement are closed, and memory used by your
>program is freed. Object references held by other programs are invalidated"
>again direct from Microsoft,
Microsoft is describing how to FORCE your application into an ABNORMAL TERMINATION.
Again, the VERY NEXT PARAGRAPH describes how to achieve a NORMAL TERMINATION.
So, your quote hardly shows Microsoft as endorsing the use of the End statement as the desired means of shutting down your program!
>What else do you worry about?? lol.
Well, let's see. There are call-back functions and subclassed processes, among other things.
Paul, just try implementing out-of-process subclassing, and abruptly end your program without replacing your Windows Procedure. You'll crash not only YOUR program, but the other program as well!
For that matter, try implementing in-process subclassing and abruptly end your program without replacing your Windows Procedure. Again, your program will crash and burn, EVERY TIME!
Now THAT is just *brilliant*!!
Besides, I much prefer Normal Termination instead of Brute-Forced, Abnormal Termination that circumvents all my code in the QueryUnload, Unload, and Terminate Event Procedures!!
Since you put so much emphasis on "DIRECT FROM MICROSOFT", (even though you completely ignore the following paragraph on achieving *normal termination*), here's another quote from Direct From Microsoft:
---MS KB Article Q129885-------------------
The End statement is convient, but it does NOT go through the complete sequence of cleaning up after your application. You should use it cautiously and sparingly when developing applications
--------------------------
FYI, Paul. "cautiously and sparingly" does not imply "all the time, and perhaps only in the Unload event of your form".
This KB Article (Direct from Microsoft), discusses a problem of an OLE Server with loaded forms not unloading when the client program (like one of yours, Paul), terminates by using the (beloved) End statement, even if the OLE server is programmed to unload its forms in the Terminate Event.
So here is how one of YOUR programs can cause grief for SOMEONE ELSE'S program, even though they did everything right.
All because YOU decided to use the END statement!
More info, DIRECT FROM MICROSOFT:
--------------------------
A Visual Basic client can destroy the last instance of an OLE Server it creates by:
- Setting it to Nothing (the preferred method)
- Shutting down by unloading the last form (acceptable, but not as desirable)
- Ending the probram by executing the End statement (this can cause problems)
--------------------------
Hmmm..... End statement not even acceptable. .... could cause problems.
But what the h--- does Microsoft know?!!!
Who do I believe, Microsoft (who created the product), or Paul__420? Microsoft .... Paul .... hmmmmm .... tough choice!
Paul, I fear that I have just turned you against Microsoft. For even they go contrary to your infinite wisdom in the use of the End statement.
But then again, this must be all hype!
Again, as to using the End statement in your Unload Event Procedure. If you're going to unload all your own forms, close all your files, unhook all hooks, etc, etc., etc., then you don't need the End statement, because your program is going to terminate anyway (NORMALLY). (No need to kick someone out the door when they are already leaving!)
>lol, I can also till you a million times not to use the END command. OK Im
>sorry guys, I guess Im just not as good as guys.
Look, I'm not trying to convice *YOU*. For you cannot push a wet noodle anywhere.
But I *can*, perhaps, prevent some beginners from falling into the pit falls you'd lead them into.
>... is because you guys are here all day, typing long ass messages. Try practicing some coding.
I get my job done early, and I do it right. That way, I don't have to waste my time debugging my programs from problems caused by using the End statement. <grin>
That gives me spare time to type these long-ass messages!
"zillions of languages" ... "rookie" ... You sound like a kid looking for an ego boost, trying to impress everyone with your (alleged) vast wealth and expertise.
::stroke:: ::stroke:: There, now does your ego feel better?
I get paid well, especially in my private practice. And I know more than one programming language. Yet I don't brag about it, nor do I proclaim my claim to fame.
Grow up and get a life!
-Dennis Borg
P.S. You can have the KB Article Q129885 e-mailed to you by sending an e-mail addressed to mshelp@microsoft.com, with Q129885 as the subject.
Or, read it here at:
http://support.microsoft.com/support/kb/articles/Q129/8/85.asp
wsh2:
>Careful DennisBorg.. this guy DOES make BIG BUCKS.. All grocery baggers
>are the ERP checkout counter are very well paid!!
ROFLMAO!! Carefull, wsh! I already fell out of my chair twice! :-)
>In being a bagboy,
All right! *That* done it! I gotta get some pillows to put around my chair! Or at least some softer carpet!
>pressing Alt-Ctrl-Del twice to END any/all of your programs is a most novel idea
Better yet, you can push only one button, one time! It's labelled "Power"
BTW, wonder why Paul hasn't added any more comments. Surely he has some wisdom which refutes my quotes that were Direct from Microsoft!
-Dennis Borg
>Careful DennisBorg.. this guy DOES make BIG BUCKS.. All grocery baggers
>are the ERP checkout counter are very well paid!!
ROFLMAO!! Carefull, wsh! I already fell out of my chair twice! :-)
>In being a bagboy,
All right! *That* done it! I gotta get some pillows to put around my chair! Or at least some softer carpet!
>pressing Alt-Ctrl-Del twice to END any/all of your programs is a most novel idea
Better yet, you can push only one button, one time! It's labelled "Power"
BTW, wonder why Paul hasn't added any more comments. Surely he has some wisdom which refutes my quotes that were Direct from Microsoft!
-Dennis Borg
I don't have a button labeled Power, I have this square one with a green light underneath of it, let me try tha@@@@,,.,.,.m.,m.,,...m
That was fun, I like that button, all I had to do was reinstall the os's and all of my programs and I was back just like new :)
>That was fun, I like that button, all I had to do was reinstall the os's and all of my
>programs and I was back just like new :)
Nothing like a clean, fresh computer to work with, right Hes? ;-)
-Dennis Borg
President PPAUES
*** News Bulletin ***
--------------------------
PAUES (Programmers Against Using End Statement) has now been renamed to PPAUES (*Professional* Programmers Against Using End Statement)
>programs and I was back just like new :)
Nothing like a clean, fresh computer to work with, right Hes? ;-)
-Dennis Borg
President PPAUES
*** News Bulletin ***
--------------------------
PAUES (Programmers Against Using End Statement) has now been renamed to PPAUES (*Professional* Programmers Against Using End Statement)
charlieosborne:
You have not given us any updates on your problem since you've posted the question.
We'd like to hear from you. I hope our having fun on this thread while we wait for your response hasn't hindered your reply.
How is this going for you? Can you give us an update?
-Dennis Borg
President PPAUES
You have not given us any updates on your problem since you've posted the question.
We'd like to hear from you. I hope our having fun on this thread while we wait for your response hasn't hindered your reply.
How is this going for you? Can you give us an update?
-Dennis Borg
President PPAUES
I guess Paul__420 is too busy debugging his trENDy programs to make any further comments.
-Dennis Borg
President PPAUES
-Dennis Borg
President PPAUES
Hes (October 20 2000 - 08:10AM PDT)
--------------------------
>I don't have a button labeled Power, I have this square one with a green light
>underneath of it, let me try tha@@@@,,.,.,.m.,m.,,...m
Hes (October 20 2000 - 08:21AM PDT)
--------------------------
>That was fun, I like that button, all I had to do was reinstall the os's and all of my
>programs and I was back just like new :)
Hes: What kind of computer do you got, that permits you to install your OS, your applications, reboot, and get back online, all in 11 minutes!!!!
I want *that* kind of computer!!! ;-)
-Dennis Borg
--------------------------
>I don't have a button labeled Power, I have this square one with a green light
>underneath of it, let me try tha@@@@,,.,.,.m.,m.,,...m
Hes (October 20 2000 - 08:21AM PDT)
--------------------------
>That was fun, I like that button, all I had to do was reinstall the os's and all of my
>programs and I was back just like new :)
Hes: What kind of computer do you got, that permits you to install your OS, your applications, reboot, and get back online, all in 11 minutes!!!!
I want *that* kind of computer!!! ;-)
-Dennis Borg
Dennis,
You got a VP or secretary yet :)
You would think charlieosborne would be running back, just to close the Q and turn off notifications LOL
You got a VP or secretary yet :)
You would think charlieosborne would be running back, just to close the Q and turn off notifications LOL
>You got a VP or secretary yet :)
No other officers for PPAUES yet. Wanna sign up? ;-)
We have some officers for PAFSO, though. Perhaps you've heard the slogan:
Just say, "No!" to FSO!!!
>You would think charlieosborne would be running back, just to close the Q and
>turn off notifications LOL
Really! ;-)
-Dennis Borg
No other officers for PPAUES yet. Wanna sign up? ;-)
We have some officers for PAFSO, though. Perhaps you've heard the slogan:
Just say, "No!" to FSO!!!
>You would think charlieosborne would be running back, just to close the Q and
>turn off notifications LOL
Really! ;-)
-Dennis Borg
Sure,
Yea got a laugh out of that one in the lounge
Yea got a laugh out of that one in the lounge
Now that's strange,
Dennis a few minutes ago I got the email of your post from 11:43 then 12 minutes later I got the notif from your post at 11:28
Dennis a few minutes ago I got the email of your post from 11:43 then 12 minutes later I got the notif from your post at 11:28
>Now that's strange,
>Dennis a few minutes ago I got the email of your post from 11:43 then 12
>minutes later I got the notif from your post at 11:28
Well, perhaps my computer *IS* faster than yours! ;-)
Or, there are some fractures in the space-time continioum (sp?), and we're being subjected to time rifts.
-Dennis Borg
>Dennis a few minutes ago I got the email of your post from 11:43 then 12
>minutes later I got the notif from your post at 11:28
Well, perhaps my computer *IS* faster than yours! ;-)
Or, there are some fractures in the space-time continioum (sp?), and we're being subjected to time rifts.
-Dennis Borg
Trendy, thats cute :) Hey honestly guys, no Secretary yet :( Good Salary tho, because Im a bomb programmer. I honestly would bet i can program circles around you guys. :)
Bye fellas. I got go work
Bye fellas. I got go work
Paul:
>Good Salary tho, because Im a bomb programmer.
You know, if you'd stop using the End statement, your programs wouldn't "bomb" (i.e. "bomb programmer")
>I honestly would bet i can program circles around you guys. :)
Your modesty simply amazes me.
Try the following out, Paul. Start a new blank project, then paste the following into Form1's Code Module.
It'll prove that I can program circles around you! ;-)
Option Explicit
Const CircleName = "Paul__420"
Private Sub ProgramCircles()
Dim Idx As Single
With Me
.Cls
.ScaleLeft = -100
.ScaleTop = -100
.ScaleHeight = 200
.ScaleWidth = 200
.CurrentX = -(.TextWidth(CircleName) / 2)
.CurrentY = -(.TextHeight(CircleName) / 2)
Me.Print CircleName
For Idx = 1 To 20
Me.Circle (0, 0), Idx * 10, vbRed
Next 'Idx
End With
End Sub
Private Sub Form_Paint()
ProgramCircles
End Sub
Private Sub Form_Resize()
ProgramCircles
End Sub
>Good Salary tho, because Im a bomb programmer.
You know, if you'd stop using the End statement, your programs wouldn't "bomb" (i.e. "bomb programmer")
>I honestly would bet i can program circles around you guys. :)
Your modesty simply amazes me.
Try the following out, Paul. Start a new blank project, then paste the following into Form1's Code Module.
It'll prove that I can program circles around you! ;-)
Option Explicit
Const CircleName = "Paul__420"
Private Sub ProgramCircles()
Dim Idx As Single
With Me
.Cls
.ScaleLeft = -100
.ScaleTop = -100
.ScaleHeight = 200
.ScaleWidth = 200
.CurrentX = -(.TextWidth(CircleName) / 2)
.CurrentY = -(.TextHeight(CircleName) / 2)
Me.Print CircleName
For Idx = 1 To 20
Me.Circle (0, 0), Idx * 10, vbRed
Next 'Idx
End With
End Sub
Private Sub Form_Paint()
ProgramCircles
End Sub
Private Sub Form_Resize()
ProgramCircles
End Sub
Paul:
>I honestly would bet i can program circles around you guys. :)
I really don't know how capable or skilled you are, or are not.
However, I do know that your apparent casual use of the End statement in every-day programming, despite the cautioning of several professionals and of Microsoft themselves, would make me uncomfortable as far as using your programs are concerned.
Let alone the fact that you seem to feel the need to convince everyone of how good you are.
Usually, the self-proclaimed experts that make lofty vague boasts about themselves are self-centered, egotistical, and conceited, and often don't have what they brag about.
Let it suffice to say, especially with all your bragging, I am *not* impressed!
-Dennis Borg
>I honestly would bet i can program circles around you guys. :)
I really don't know how capable or skilled you are, or are not.
However, I do know that your apparent casual use of the End statement in every-day programming, despite the cautioning of several professionals and of Microsoft themselves, would make me uncomfortable as far as using your programs are concerned.
Let alone the fact that you seem to feel the need to convince everyone of how good you are.
Usually, the self-proclaimed experts that make lofty vague boasts about themselves are self-centered, egotistical, and conceited, and often don't have what they brag about.
Let it suffice to say, especially with all your bragging, I am *not* impressed!
-Dennis Borg
ASKER
I doubt any of you guys are reading this anymore as you probably can't post comments anymore (I don't really know how this site works yet - new here, adn to programming as you may have guessed!)
The reason I wasn't saying how I was getting along was because somebody else already answered my question and my internet connection got screwed up for a while too - oh yeah, and I found it quite amusing just reading what you guys were writing to each other. Sounds like you guys in teh "real world" (I'm just a student still!) don't actually do much work, or at least manage to enjoy it when you do.
Cheers for all your help, it was very insightful adn amusing, Charlie
The reason I wasn't saying how I was getting along was because somebody else already answered my question and my internet connection got screwed up for a while too - oh yeah, and I found it quite amusing just reading what you guys were writing to each other. Sounds like you guys in teh "real world" (I'm just a student still!) don't actually do much work, or at least manage to enjoy it when you do.
Cheers for all your help, it was very insightful adn amusing, Charlie
' Try to end this thread
END
END
Rejecting Reel's answer.
If no objections are made in the next 5 days, I will force accept hes' comment.
costello
Community Support Moderator @ Experts-Exchange
If no objections are made in the next 5 days, I will force accept hes' comment.
costello
Community Support Moderator @ Experts-Exchange
No objection here.
What can I say :)
>What can I say :)
I take it that you don't object, hes? ;-)
I take it that you don't object, hes? ;-)
Allright, force accepting hes' first comment in this <amusing> thread.
costello
Community Support Moderator @ Experts-Exchange
costello
Community Support Moderator @ Experts-Exchange