Andrew11
Quote: "Ill admit goto is not good to use too often, but in some places, its ok to use. It really dosent hurt your program."
If DBP supported "On Error Goto" then I would agree with you on this, but unfortunately dbp does not, so I must say that there is NEVER a time you should use goto. Never. Not when you have GOSUB available. If you find yourself using goto instead of gosub then there is a problem in the code logic. I am sure most vet programmers here would agree, and mind you I said "Not when you have GOSUB available". I am just trying to state that GOSUB is much more reliable and safe as it implies RETURN. Goto is open-ended and dangerous and will get you spaghetti-code(sp?) in the long run - for sure!
Quote: "But whats wrong with changing the variable in a For Next loop??? What is the difference??? What does it do thats "very bad"???"
Well, for me, if I define a FOR-NEXT loop to be some range of numbers then it was for a reason. Altering the outter loop count, to me (IMHO) seems silly and unecessary when you have all sorts of condition tests at your disposal. Maybe I am used to collections and the inherent FOR EACH-NEXT way of doing things in vb6/.net but it just seems if you need to change the variable that the whole loop is based on then something is very wrong - sorry i can't explain it better than that
_ not trying to be a wise ass here, really, just trying to trickle down some observations based on my coding experience. Regardless of the language, some base principals hold true.
In the end, do what works best for you!
JAM
-RUST-