Re: Would you believe Windows XP market share went UP last week?
Actually no. There are many things which aren't compatible.
For a start any version of Internet Explorer later than a certain version simply won't work with Visual Studio 6. So, if you use any of the controls that came with VS6 then it won't work. That issue is none of my doing.
Secondly, the code uses a lot of ADO because it works and that was the bees knees at the time. With XP I can blat out about twenty thousand queries and no end of operations on the resultant recordsets (each day's run may have over a couple of million iterations through all of the recordsets). All of the designs were the right design of the day and to MS' own approved methods.
Having said that; the quality of my code actually surpassed MS' own samples in the MSDN. This wasn't hard because, for example, MS were not very good at using data types in their examples.
On W7 machines and later this just chokes after lots of thousands of databases queries. The problem is, again, the lack of backward compatibility. Yes, I have tried to change the Connections and about everything else I can think of without going from the ADO.
But the point is. That the code that I wrote was to standard at the time. Not only that; I used Microsoft's own compilers, on their own operations systems against their own databases and to their requirements, specifications and standards and then along comes .Net and Windows 7 and what they've done is to ignore what was done in the past and made no real attempt at backward compatibility.
I know of other developers who have similar issues. On my main machine here I can at least load the application into Visual Studio because I have an old version of Internet Explorer. On my newer machines I can't even load the source code into the IDE because of the browser.
This last point. I fail to see how this is my fault. Anyway, myself and others all say the same thing: if we can load the code into the compiler then we can't compile it because that doesn't work for large Visual Studio applications. I don't know how large it has to be before it all breaks but I have an application with about 100 classes, dozens of modules, around fifty forms and the compiler breaks on Windows 7 machines.
Again, that isn't my doing.
That's why I need XP machines because MS have really buggered things up. And there's more than just the two of us with this problem: there must be billions of lines of code out there that works and was written well and to spec which still has to be supported.