I still use VB6 because I'm a one-man shop supporting a couple of apps that I've developed over the course of 10 years. I went to a VB.Net class in 2003(?) and started the migration from VB6 to .Net. I had several failed starts. Just when I would be making some progress, there would be some new initiative to add to the existing (VB6) codebase, and the VB.Net would get back-burnered. At this point I'm closer than ever to getting the larger of my two main apps converted. It's still months or more away, though.
Overhead is a factor, I think. Sure there are lots of nice little features in VB.Net that should make things *seem* faster. But, it's not! And, there's a learning curve involved with exploiting those features besides.
My understanding is that Micro$oft hasn't converted all their apps to .Net. Why should they expect that I/we can do what they can't/won't?
One thing I have noticed about VB6 users over the years is that they are a group that just won't die. Even if Microsoft cuts the cord on VB6, they will some how find a way. I think they inspired the line in Jurassic Park where they find the eggs and say "Nature finds a way". Just replace "Nature" with "VB6ers"
Funny the 'no more support' story. With my MSDN Subscription I can still download old VB Versions...
I updgraded from VB 6 to 2003, then from 2003 to 2005 (a bad move here as the 2005 was so unstable before the service pack, then from 2005 to 2008 with sp1 (best thing ever), now from 2008 to 2010 (lots and lots of problems, the report writer from SQL had changed as well). But at least Team Foundation Server is cheapter now and that Helps tons...
Microsoft tries to age out the crap is doesn't want to deal with, like any other company. However, if a large enough customer still uses type writers, IBM will still provide them. My sense is that a few major players can't cut the VB6 cord. Until they do, VB6 will remain in it's undead state.
I must admit, I always assume most of our VB6 questions come from the same backwaters that haven't abandoned Turbo C. It doesn't surprise me VB6 is still used in the wild; so is COBOL. What surprises me is that people write new programs in it.