It isn't just MS. For example, the software that the government uses to determine MediCare reimbursements has over ONE MILLION documented bugs. IBM at one time, and still may, had a policy that when the ratio of bugs to lines of code reached a certain point, the software was considered stable and released. It isn't just an MS issue. It affects every software developer and company.

Again, I'm not sure additional QA would have caught this error.


>>>Or do it the RIGHT way and make a recall.
>>
>>I disagree. That would mean a recall would have to be made of just about every application ever written. ANY application of any complexity goes out the door with bugs.
>
>The problem is that everyone has grown numb to MS bugs. It's part of the cost of doing business with MS. MS passes that cost to it's customers.
>
>Many IT environments have to thoroughly test bug fixes before the patches are applied to all the machines. This costs alot of money. While this is expected in our industry, MS sets shoddy standards with it's quality control in the name of getting the product out the door. This policy accelarates their cash flow at their customers expense.
>
>Granted, recalls are not the answer - better Q&A is. And we all know that unless alot of noise is made about a particular issue, MS will do nothing.