Torfnasen töten: When End User Managed Applications cause critical errors

A furious blame game is under way today after 16,000 coronavirus cases were missed due to a computer glitch - meaning thousands more potentially infected contacts were not traced. The extraordinary meltdown is believed to have been caused by an Excel spreadsheet containing lab results reaching its maxium size, and failing to update.

Some 15,841 cases between September 25 and October 2 were not uploaded to the government dashboard. As well as underestimating the scale of the outbreak in the UK, critically the details were not passed to contact tracers, meaning people exposed to the virus were not tracked down.

At some point you have to move data from a personal productivity tool into a serious database. Microsoft Excel spreadsheets can contain up to 16,384 (16 x 1024) columns and 1,048,576 (1024 x 1024) rows. You should no wait until you hit those numbers.

This is not human error, nor is it an Excel glitch. It's end user managed applications without developer support and proper testing. That is organizational failure, and a deadly one.

More >


Exactly. Thanks for the clear words.

Hubert Stettner, 2020-10-05

Nothing much has changed in six years.

Jan-Piet Mens, 2020-10-05

My words exactly. We provide database solutions for higher education. When I speak to prospects, they often say "we already have a system in place that works just fine" (sic!). When I dig deeper, it usually turns out that their "system" is Excel.

They usually get back to us eventually, when they realise that Excel is not made for these purposes and has its limitations, when it comes to storing and managing data.

Axel Borschbach, 2020-10-05

(Vorsicht: Quelle ist Daily Mail)