• Quick note - the problem with Youtube videos not embedding on the forum appears to have been fixed, thanks to ZiprHead. If you do still see problems let me know.

MS Excel

Spill functions are also ace. When these came out, it was a step move for my spreadsheets. As I hate pivot tables, these were a real step forward.
 
The acceptance of Excel spreadsheets as the computation requirement for licensed engineering work is kind of a game-changer. It has saved us quite a lot of time.

However, I have found the quasi-database features of Excel to be a source of endless headaches and rework. I will continue to question any attempt we make to use Excel as if it were a relational database.

The worse misuse I have ever seen was by a project manager (happily now departed) who used Excel to draw a conceptual schematic. He resized the rows and columns, combined cells, and used the border feature to create boxes and lines. I kid you not. I'd post a picture, but it has a lot of proprietary information in it. If I get bored enough to redact it, I might post it later.

And of course :—

Screenshot 2026-01-13 at 9.55.02 AM.png
 
Just for old times' sake, anybody here remember Lotus 1-2-3?
When I started out, spreadsheets were just lined pieces of paper that we filled in with pen, and a simple "what-if" was two hours with the door to my office closed and hold my calls. We eventually got an early IBM PC with Multiplan, Microsoft's first attempt at a spreadsheet. It was misery-inducing. If you wanted to type a label, you had to first type A for Alpha, or else the computer would assume you were typing in a series of commands. When Lotus came out one of the smartest things they did was making labels the default, and hiding the commands behind the / key--made things much easier. But by the early 1990s, my favorite spreadsheet was Quattro Pro. Unfortunately since Excel was what most of my clients used, I was dragged kicking and screaming back into a Microsoft product. I've fiddled around with some others since then but came to accept Excel eventually.
 
And if you tried using Excel as a word processor you'd probably run into lots of other problems. Excel has its uses and does have some simple database-type functions like sorting, and at times you can tease out data using "if-then" formulas. If you really want to do more sophisticated data analysis, it's much better to use Access. I commonly used Excel to fill in forms that I then pasted into Access, ran a few queries and pasted the results of those queries back into Excel so I could present it however I wanted.
I often use Excel to check data in Access, as there are often errors, and they show up easier in Excel. I can then correct the errors in Access.
 
I use Excel often enough for data visualisation and some quick and dirty first level analysis, even if I'm only familiar with a tiny subset of its functionalities. But I'm enough of a coder and control freak to be very hesitant about using it for anything too complicated.

When I started my career we used to map out trial balances on A3 sized sheets of 14-column paper, with pencils and a lot of swearing. Moving that onto 1-2-3 was a big step forwards for us.
 
I bet these guys do:

More broadly though, you don't need to know everything about Excel to use it. Most uses don't need the more obscure functions and work arounds.

I think one of the things about it that people here are critical about, is that it can be self taught. You can start making calculations with only the most basic of knowledge, and as your needs expand, you can find out each function as you go, and its all very intuitive. Of course, this can lead to bad habits, which can lead to the problems above. But also relying to much on pivot tables, which can cause so many problems.

Compare this with creating a database - I wouldn't know where to start, and I once went on a one day Access course. I just don't have the time to sit down and learn from scratch how to build one, and I'm currently looking at buying one for our site as our old Access database is struggling. The alternative is finding someone to make one from scratch, but I'm not sure our large company would go with that.

I've often wondered how many businesses have died because 'someone set up an Access database'.

There was a rule of thumb where I used to work: "No matter what the problem is, Access is not the answer".

We'd been asked to fix Access disasters so many times, the Director had put out an edict: "If anyone wants assistance with an Access database, the answer is always 'no'."

Generally "end user computing" in a corporate environment, is a disaster.

A former employer performed an internal audit and found that there were thousands of employees maintaining spreadsheet methods for recording time worked.

Every single one of those employees was supposed to be doing something else.

(NB. The organisation had 45,000 employees.)

Of the thousands of different methods that were being developed, they were able to find exactly zero that were correctly calculating hours worked etc.

What a waste of effort.

(The original investigation was started because employees were handing in so many timesheets containing so many errors, it was bogging down the payroll area.)
 
But you don't need to know all the functions, just the ones you need to accomplish your task.
It's called the 80/20 rule. 80% of people use 20% of the features.

Just for old times' sake, anybody here remember Lotus 1-2-3?
I supported and used Lotus Notes, 1-2-3, Word Pro, and Sametime. Domino was the big new thing.
 
There was a rule of thumb where I used to work: "No matter what the problem is, Access is not the answer".
It's on my company's list of disallowed tools.

A former employer performed an internal audit and found that there were thousands of employees maintaining spreadsheet methods for recording time worked.
My spouse's law firm tolerated this for years, but in this case it was an unofficial Excel spreadsheet hacked together by a 2L intern. Sadly, that was pretty advanced for the time. Lawyers are notoriously impervious to technology.
 
I saw far too many spreadsheets that should have been tables in Word.

Spreadsheets are for crunching numbers. You want tabulated text, you use Word.
 
I saw far too many spreadsheets that should have been tables in Word.

Spreadsheets are for crunching numbers. You want tabulated text, you use Word.
I've seen too many tables in Word that should have been tables in LaTex.
 
So, what do you use instead?

Something scalable, maintained by professionals, so it doesn't suddenly bite you in the arse.

The worst part was the Access systems, where data should have been in one of the corporate tools, so that the information can be used by people outside of your own, individual team.
 
Yes! I've been watching her videos all month, I'm working right now (okay, later today) on the dependent dropdown method she teaches to select data from a FILTER array.

Also good are "Kenji Explains", he does step-by-step guides on how to build things: Kenji Explains
I did a whole day working on dependent dropdowns a while ago. Most methods (like this one) are ok if you only have a few categories and 2 levels, I was working on a 3-level category list with nearly 200 combination options (the method works for multiple levels). Got there in the end, all working off one source table as well. The function isn't pretty, but doesn't require maintenance to pick up changes - just update the underlying table and it all cascades through. Damned if I can find the source for it though, forgot to bookmark.
 

Back
Top Bottom