Abraham & Erwig (2007)Spreadsheet errors have resulted in huge financial losses.
Sakal, et al (2015)Overconfidence is one of the most substantial causes of spreadsheet errors.
Kruck & Sheetz (2001)...few incidents of spreadsheet errors are made public and these are usually not revealed by choice.
Panko (2015)Research on spreadsheet errors is substantial, compelling, and unanimous.
Galletta, et al (1993)Even obvious, elementary errors in very simple, clearly documented spreadsheets are... difficult to find.
Burnett & Myers (2014)The software that end users are creating... is riddled with errors.
Dunn (2010)Spreadsheets are extraordinarily and unacceptably prone to error.
Caulkins, Morrison, & Weidemann (2008)Spreadsheets are commonly used and commonly flawed.
Abreu, et al (2015)Spreadsheets can be viewed as a highly flexible programming environment for end users.
Hermans & van der Storm (2015)Spreadsheets are the most popular live programming environments, but they are also notoriously fault-prone.
Panko & Ordway (2005)Most large spreadsheets have dozens or even hundreds of errors.
Panko (2008)94% of the 88 spreadsheets audited in 7 studies have contained errors.
Chadwick (2002)Spreadsheet errors... a great, often unrecognised, risk to corporate decision making & financial integrity.
Raffensperger (2001)Never assume a spreadsheet is right, even your own.
Mireault (2015)Developing an error-free spreadsheet has been a problem since the beginning of end-user computing.
Bishop & McDaid (2007)The quality and reliability of spreadsheets is known to be poor.
Nixon & O'Hara (2010)It is now widely accepted that errors in spreadsheets are both common and potentially dangerous.
Irons (2003)Spreadsheet errors are pervasive, stubborn, ubiquitous and complex.
Bock (2016)Spreadsheet development must embrace extensive testing in order to be taken seriously as a profession.
Caulkins, Morrison, & Weidemann (2006)People tend to believe their spreadsheets are more accurate than they really are.
Beaman, et al (2005)Errors in spreadsheets... result in incorrect decisions being made and significant losses incurred.
Kulesz & Ostberg (2013)Spreadsheets are more fault-prone than other software.
Paine (2001)Spreadsheets are alarmingly error-prone to write.
Ross (1996)A lot of decisions are being made on the basis of some bad numbers.
Colbenz (2005)Errors in spreadsheets are as ubiquitous as spreadsheets themselves.
Panko (1999)Every study, without exception, has found error rates much higher than organizations would wish to tolerate.
Mireault & Gresham (2015)Spreadsheets are often hard, if not impossible, to understand.
Sajaniemi (1998)The results given by spreadsheets are often just wrong.
Durusau & Hunting (2015)Spreadsheets are dangerous to their authors and others.
Panko (2014)Despite overwhelming and unanimous evidence... companies have continued to ignore spreadsheet error risks.
Murphy (2007)60% of large companies feel 'Spreadsheet Hell' describes their reliance on spreadsheets.
Krishna, et al (2001)Programmers exhibit unwarranted confidence in the correctness of their spreadsheets.
Panko & Halverson (1996)Every study that has looked for errors has found them... in considerable abundance.
Csernoch & Biro (2013)Studies have shown that there is a high incidence of errors in spreadsheets.
Howard (2005)Spreadsheets... pose a greater threat to your business than almost anything you can imagine.
Panko (2013)It is irrational to expect large error-free spreadsheets.
Chen & Chan (2000)Spreadsheets are easy to use and very hard to check.
Abreu, et al (2015)Despite being staggeringly error prone, spreadsheets are a highly flexible programming environment.
Teo & Tan (1999)Most executives do not really check or verify the accuracy or validity of [their] spreadsheets...
Caulkins, Morrison, & Weidemann (2006)Your spreadsheets may be disasters in the making.
Rust, et al (2006)Spreadsheets have a notoriously high number of faults.
Cunha, et al (2011)Spreadsheets are notoriously error-prone.
Powell, Baker, & Lawson (2009)1% of all formulas in operational spreadsheets are in error.
Nixon & O'Hara (2010)Spreadsheet errors are still the rule rather than the exception.
Price (2006)The untested spreadsheet is as dangerous and untrustworthy as an untested program.
Reschenhofer & Matthes (2015)Spreadsheet shortcomings can significantly hamper an organization's business operation.
Abraham, et al (2005)Spreadsheets contain errors at an alarmingly high rate.
Miller (2005)Untested spreadsheets are riddled with errors.
Panko (2007)The issue is not whether there is an error but how many errors there are and how serious they are.
Ayalew (2007)A significant proportion of spreadsheets have severe quality problems.
One of the nice features of Excel Tables is the banded row formatting, which makes it easier to read and scan your data.
Unfortunately Excel Tables aren't efficient with large data sets (over 100k rows), but we can replicate the banded rows with Conditional Formatting, and we can toggle it on and off at the click of a button, as shown in this blog.
One of the most powerful features of Excel formulas is the ability to create absolute references that don't move around when you drag to extend cell formulas or copy them to different places in your spreadsheet.
When you start using data tables in Excel, many users are frustrated to discover that the normal methods for freezing the row or column references don't work! This can make it time consuming to build your spreadsheets when they use tables.
Fortunately, there are some workarounds! We'll walk through a few of them in this quick tutorial.
Like operator allows you to match a string to a pattern in Excel VBA.
This blog describes usage of the VBA
Like operator and, as a bonus, mentions how you can use the question mark
? and asterisk
* for pattern matching in many Excel functions
Like operator uses the following patterns:
?(question mark) - Matches any single character.
*(asterisk) - Matches zero or more characters.
#(number or hash sign) - Any single digit.
[abc]- Characters enclosed in brackets allows you to match any single character in the string.
[!abc]- The exclamation mark (
!) matches any single character not in the string.
[A-Z]- The hyphen lets you specify a range of characters.
This post provides a complete guide to VBA error handling.
Topics covered include:
Transparency is important to auditors and to those who commission models because the less transparent a model is the longer it takes to audit and the more it costs to deliver.
I have never seen a 'transparency' measure yet modelers claim one method is more transparent than another. How do they know? The short answer is, they don't because no one, that I know of, measures model transparency.
This article proposes a metric for Excel model transparency. A model's transparency is the sum of components for:
This article presents an overview of recommended Excel modeling best practices:
An Excel pioneer, Peter Bartholomew, likes to create Excel names using odd characters.
For example, he uses a
? at the end of a name to identify it as a Boolean value like
TRUE/FALSE. He also uses
← to indicate the name points to a prior value.
I like his concept. But I was shocked to see his names because I was led to believe those characters were illegal.
I checked my sources which include Microsoft's reference and the best VBA websites. None of them provided a complete list of invalid characters and some were just plain wrong.
So I rolled up my sleeves and wrote some code to create Excel names using the ASCII standard (first 255) character set:
Named ranges are one of these crusty old features in Excel that few users understand. New users may find them weird and scary, and even old hands may avoid them because they seem pointless and complex.
But named ranges are actually a pretty cool feature. They can make formulas *a lot* easier to create, read, and maintain. And as a bonus, they make formulas easier to reuse (more portable).
This article has 20 tips for creating and using named ranges in Excel, grouped as follows:
This article provides a comprehensive introduction to the use of Class modules in VBA.
Topics covered include: