Re: Hmmm @Mage
To be fair, VB6 as a language was very broken by that point. They needed to fix it, and doing so was always going to break compatibility.
Backwards compatibility has always been both a strength and a weakness of MS. They were maintaining behaviour in XP and beyond that dated back to bugs in DOS. There comes a time when you have to say "this is too broken, we're going to depreciate it in the next version and remove it from the next". The trick is to do this at a speed that the developers and users can handle.