23/02/2021
A while back you may recall a bit of a fuss over a government spreadsheet that failed to transfer some Covid testing data from A to B, and the rumour was that it was because of an out-of-date version of Excel limiting the amount of data to some 65000 rows instead of the current million or so.
Interestingly, a client of mine has just had the exact same problem, which manifested itself as a number of customer complaints following the sending out of essentially blank emails notifying said customers of some information.
Having exhausted all the normal avenues in trying to determine why this data had failed to turn up as expected, we looked at the spreadsheet being created by a legacy application designed to extract it from the source ready for import into the destination.
Sure enough, one of the tabs was "full to the brim" - 65000+ rows.
What only a few of the news stories last year pointed out was that the issue is not the version of Excel you are currently using (these guys are on the latest Office 365 version), but the "format" of spreadsheet created by a third-party application.
So if I create a *.xls file, it will be the old Office 2003 format, but if I create a *.xlsx file it will be the latest format. Most export routines use various libraries that create the appropriate format, so an "old" format written to a "new" Excel version will be limited to the 65000 rows.
It's important, therefore, not only to ensure that your software versions are up to date, but also that any legacy applications are also kept in line. It's fairly common for people to export comma-delimited text files as "CSV" documents, and then to open them in Excel, running the risk of damaging the formatting if they then save it.
This capacity issue adds a new level of excitement, but now it is one that we will be looking out for much earlier in the process of diagnosing an issue!
(Photo by Mika Baumeister on Unsplash)