We experience this all the time when there is some kind of failure. The hardware snobs blame it on the software/programmers, and the programmers blame it on the hardware. Our software has been funning in about 100 stores for over 10 years, so 99.99% of the time the problem is hardware or someone shut off the power in the middle of a process.

>There were six of us FoxPro Programmers working together with as many VC++ developers near by. We got blamed for “everything” by the VC++ guys as “FoxPro is an inferior product”. Two examples were:
>
>1. Memory leak. The application was a 24/7 and would fail in less than 24 hours due to a memory leak. The VC++ guys had their heads in the air and blamed us. We proved it was their problem and even found the code causing it. That was one for us!
>
>2. A new version of FoxPro was installed on the Network running NT and Novell. When ever anyone would attempt to access it the entire network would shut down. Since there were about 250 people in the office this managed to get everyone’s attention. We became famous and jokes over the company P.A. system let everyone know “we were guilty”! “See how terrible FoxPro is? It shut down the network! Get rid of it”!
>
>The network problem shut down the company for over 24 hours and turned out to be a bad segment on the hard disk. Whenever anyone went to access it, it would kill the entire system. We were spared once again.
>
>That incident convinced me to not become a Novell CNE, as I had planned. I saw the network tech pull a 32 hour shift with no rest. Enough!
>
>There is something about computers I love and then again…