> On error resume next: This can be scoped. So I’m reality it’s was used in small sub routines where errors needed to be discarded. Your “in reality” sounds a

> On error resume next: This can be scoped. So I’m reality it’s was used in small sub routines where errors needed to be discarded. Your “in reality” sounds a lot nicer than mine. In my experience “On Error Resume Next” was slapped right at the top of every single lovecraftian horror that was a VB6 file, like a prayer to gods who had clearly abandoned humanity. Engineering inventory management? On error resume next. Departmental budget management? On error resume next. Telecom billing rectification? On error resume next. Was there some sane way to use it? Sure, probably there was a team, somewhere, somehow, using this language and making safe, sane, and well-reasoned decisions on how to best take advantage of its features while avoiding its sharpest edges. But the first thing I learned in this industry is that if you try to teach the average VB programmer to fish, they’ll have burnt down the village and strangled themselves in the line by lunchtime.