>>Terry,
>>
>>SNIP
>>
>>I really am always amazed when software errors are so wilfully tolerated when errors in virtually any other kind product are definitely not tolerated. My guess is that it is us, the developers, who are the primary proponents for this stand and it likely has much to do with our own needs to have ass-cover for our own problems.
>>
>>regards,
>>
>>JimN
>
>I don't like bugs. I'm proud. You're proud - and I'm sure we both could bet the MS Fox group (as well as the other MS disciplines) are proud. We like doing good work. Maybe I don't push the envelope - but I like to think I do. When I'm forced to write work-arounds - I am not sure if it's a bug or my mis-use of the paradigm - that got me to that point.
>
>However, I do just one thing - write applications. I don't venture into administration or configuration - except requiring that all PC's are pentium and all printers HP. But a lot of the people - and you maybe one - provide a broader spectrum of service. So you may have a good point. I have the luxury of pleading ignorance :-).
>
>.. but I do lurk through the bug and error threads - just to be safe.
>Terry

Terry;

You brought up a very important point. In my contracts for all my consulting work I specify what hardware and drivers will be used. This is done with the assistance of the client. Some hardware clients use is O.K. and some is not. I have my list of "what does not work" that I am aware of. Most client systems are O.K. just as they are configured. Others are "computers from hell"!

If the client changes a video card or anything else after I deliver an application and has a problem, I know where to look first. This has been working for the last 19 years and helps to attain fewer problems.

One client bought all new computers from the same vendor (well known) and my program did not work on one of them. It turned out to be the BIOS was an old version and had some known problems.

The problem with this industry is that there are so many dependencies. As developers we have to have enough experience to know what network problems might exist, hardware, software conflicts, etc. Jack of all trades and master of many is what the typical developer has to be.

The great thing about the UT is someone out there can solve just about any problem. All that we have to do is ask. This is a very talented group of professionals and they give a lot of themselves to help each other!

Tom