no1zson> What is wrong with GOTO?
It usually is misused and it has the potential of making any code hard to debug and maintain.

no1zson> What would you suggest in its place?
Ideally, a sharp mind with the ability to design a flow control from top to bottom.

Meaning if it was not misused there is no issue?

Perhaps it is my lack of experience, but I would think a sharp mind might also weigh the possibility of future POTENTIAL issues against this program's simplicity and the cost of re-coding something that already works and find no real reason to remove it.

The only times it should ever be used are of the most rarest situations.
So don't get any ideals about using in substitution of well planned logic.

Thanks.
I was hoping that was well planned logic! lol

Shows what I know.