VB to VB.NET was more to do with .NET arriving with the .NET Framework, and one of the reasons for the .NET Framework was all about keeping up with the (at the

VB to VB.NET was more to do with .NET arriving with the .NET Framework, and one of the reasons for the .NET Framework was all about keeping up with the (at the time) amazing framework/core library that Java had. It was also about web front ends which of course VB6 could not do. In the old days people used to custom-build massive CRUD desktop database applications for their company to use internally and I built some of those in VB6. Loads of UserControls nested inside each other, solutions with multiple DLLs, you could do it but it was really clunky. Error handling was rubbish. I had also built things in Java and could see what VB6 was missing. .NET fixed that. So I guess the 3 percent of Visual Basic 6 bus drivers who actively wished to become fighter pilots were probably people who had used Java. Java was free, if you didnt want an IDE. Whereas VB6 was actually quite expensive (can anyone remember the cost of a VB6 Pro license?)