>>First almost everyone complains about when the product is going to be available, which obviously puts pressure on the Microsoft staff to get the product out. Then when the product is released with speedy fixes, you complain about not having the product held back until the fixes have been applied to the shipping product. You can't have it both ways.
>>
>>Also, how many of you always deliver your programs to customers 'bug-free'. Bug free software is an oxymoron and if you say that you deliver bug-free software you are only fooling yourself.
>
>It's a question of degrees. If you think the quality of the current release is acceptable, then I disagree. And if you think "buggy software" is to be expected / accepted, then again, I disagree. If your position is intended to be a cushion for any future "buggy" releases that you might deliver, then I disagree. If you treat your Users, as you expect to be treated, then I might agree. If you think that "buggy" software is a fact of life, I suggest you find another line of business. If you think that airplanes are destined to "crash", then maybe software IS your calling. If you are considering the medical profession; please DON'T.

I was hoping to get some reaction to my statements and I did. First, before our company even considers releasing a new version on our software: www.marathonsystems.com, we run it through multiple test cases using every possible combination of data. Then we let non-programmer in-house users test it for both usability and debugging. Only then does it get released into the real world. In most cases users will always enter data a certain way or use some combination of data entry that causes the software to hickup. This does not happen very often, but when it does we strive to rectify the situation as quickly as possible. If the user knows that you are on top on the situtation, or better yet you have released a fix almost at the same time as the actual release (as per Microsoft), before the user or their business is impacted by the bug it has been corrected.

I don't think 'buggy' software is a fact of life, but even after countless hours of testing and retesting, some combination of data and/or user requirements will allows that pesky bug to appear. I have never met a programmer yet who is perfect (I started programming in 1979) and can produce code that works 100% the way it was designed the first time out of the box. I'm not talking about simple 1000 line programs, I am talking about sophisticated business applications.

I am also not a great fan of Microsoft in alot areas, but lets get real here. I would rather have a quick reaction to minor/major bugs like they have given us than sitting on it for weeks or months like we have seen with some of there other products.

The reason I titled my thread WHINERS is that I see alot of energy spent complaining on the Universal about everything the Fox people do and it is not productive. Get out there and produce/sell Visual Foxpro applications and spend less time waiting for Microsoft to do your job for you.


P.S. I am flying my twin engine Cessna from Salt Lake to Vancouver tommorow to assist my best friend (she's a doctor) in her first open heart operation.