A couple of points.

1. If you are releasing activex controls to your clients, which they incorporate into vb projects then it is their problem if they use End statements. In the same way if you release a financial app and the end user refuses to following the instructions, then no amount of tweaking the code will fix it.

2. Chockenberry have you ever worked in the real world. Yes GoTo leads to bad code if it is applied without defined standards. Try explaining to a Bank that you have just slowed down their systems through removing all GoTos from their programs. In some cases you need the speed of GoTos, you don't want the GoSubs because of extra lines of code being executed. The first job l had as a programmer was for a bank maintaining COBOL code, yes it was fill of GoTos. The GoTos were used to speed up processing.