Schools can't just change their cirriculmn overnight... there's certifications involved and it has to be in compliance with what other schools are doing. This is what makes grades and credits transferrable. If I take a.NET class at a local university, then transfer to another one that doesn't have a .NET cirriculm I lose out... those grades will not transfer. Changing development languages - changing ANYthing about course work isn't easy. That's why VB6 is still in use in a lot of educational places.

Esposito - All that means is that twice as many people have problems with VB6 than they do with VB.NET. And just because some one is viewing one forum vs another doesn't mean squat.

As for VB going open source... even if it were to happen, it's written in C. Those that would be interested in keeping VB6 around so they could use it would need to learn C to keep it alive. Somehow I don't see that happening. The legions of VB users out there do so for a reason, so we wouldn't have to use C/C++ .... If I'm going to learn C to just keep VB alive, then I might as well switch to C and get the benefits of that.

-tg