The cosmic perspective reminds us that in space, where there is no air, a flag will not wave - an indication that perhaps flag waving and space exploration do not mix.
One of the things I repeat over and over in my Microsoft Access classes is this: don't delete data. I even have an entire video about it. I don't care if a customer died ten years ago - don't delete them. You discontinued a product in 2017? Don't delete it. And no, you shouldn't be wiping out old orders just because they "clutter up" your database. That clutter is your business history. You don't throw away your past just because it makes the screen look busy.
The better solution is simple: add an IsActive field. Checkbox, Yes/No, whatever. Mark inactive stuff as inactive. Then filter it out of your dropdowns or reports. That way you keep the historical record, but you don't get bogged down in legacy entries when working with current data.
Because trust me, you'll want that data someday. Maybe not tomorrow, maybe not next week, but eventually you'll be kicking yourself: "Who was that customer from Nebraska who placed that weird custom order back in 2014?" Too late. You deleted them. Good luck digging through old backups - assuming you even have them.
And this principle doesn't just apply to databases. It shows up everywhere.
Take science. According to a recent report, NASA is being pushed to destroy a perfectly functional satellite that monitors carbon dioxide levels in Earth's atmosphere. Not because it's broken. Not because it's obsolete. But because the data it collects is politically inconvenient. It's doing its job. The data is valuable. And someone in power wants to delete it. Literally. They're planning to deorbit it so it burns up on re-entry when it still has plenty of life left.
This isn't just bad science policy. It's a fundamental misunderstanding of how information works. You don't delete data because you don't like what it says. You analyze it. You challenge it. You try to understand it. But you don't throw it into the fire.
It happens in personal life too. Ever notice someone with a mysteriously empty text history? No messages older than a few days, no conversations saved? No browser history? It's usually not a good sign. Either they're hiding something, or they're so obsessed with control that even their past can't be allowed to exist unfiltered. (1) Either way, it's not a healthy relationship - with information or with people.
Same goes for fitness. I've had friends tell me they deleted their old food logs or weight entries because "those were bad weeks." But that's the whole point. Tracking only your best days isn't accountability - it's storytelling. And storytelling doesn't help you get stronger, eat smarter, or stay consistent. Progress is messy. That's why you track it.
Even in politics, you'll see attempts to erase, rewrite, or bury the past to make current decisions look better. That never ends well. The first thing authoritarian regimes try to do is rewrite the history books. Not just to clean up the past - but to control the present. Sometimes that means silencing watchdogs, gutting transparency, or even replacing the people in charge of collecting inconvenient facts. But shooting the messenger doesn't change the message. If the numbers are bad, you fix the policy - not the person reporting them. You don't fire the weather forecaster because you don't like the forecast. You bring an umbrella and figure out how to build better shelter. Ignoring the data doesn't protect you. It just makes sure you never see the storm coming.
And of course, Star Trek saw this coming. In the TNG episode "The Pegasus", Captain Picard discovers that his trusted first officer, Commander Riker, has been hiding details of an illegal and dangerous experiment from a past mission. Starfleet had buried the incident. Records were sealed. Details scrubbed. The official story didn't match the truth. And that truth nearly gets everyone killed. When Picard finds out, he's furious - not just about the experiment itself, but about the cover-up. "You don't hide from the truth," he tells Riker. "You face it. Even when it's ugly." That's what data is: the record of what actually happened. Bury it, and you lose the ability to learn from it.
Deleting data isn't just a technical decision. It's a philosophical one. Are you trying to understand the world? Or are you trying to curate a version of it that makes you feel more comfortable?
That choice shows up in Access databases, in scientific labs, in relationships, in fitness apps, and in bridge logs aboard the Enterprise.
So once again, for the people in the back: don't delete the data. Mark it inactive. Archive it. Filter it out if you need to. But don't pretend the past didn't happen.
That's how mistakes get repeated. That's how systems break down. That's how people start flying blind.
(1) And no, deleting your text history "to save memory" hasn't been a valid excuse since about 2004. Storage isn't the issue. It's the story you're trying to erase.
No, here in the States we don't have any kind of federally mandated "you must delete data" laws like you guys do with GDPR. There's no national standard for data deletion. Even at the state level, most places don't require it. Florida definitely doesn't. A few states like California, Colorado, and Virginia have passed privacy laws that encourage minimizing data retention, and they give consumers the right to request deletion, but that's not the same as a blanket requirement to automatically delete data after a certain date.
That said, implementing something like a KeepUntil field wouldn't be hard at all. It's basically the same logic as archiving old data - except instead of copying it to another table, you'd just delete it outright. Same pattern, different action. Definitely something that could be its own mini-series of videos. Adding it to The List... LOL.
Actually, what do you guys think? Should I make The List public again?
For those of you who haven't been around that long, I used to have something called the Waiting List. It was a giant page with all the courses and seminars I had planned, and you could vote on what you wanted to see next. I tried to prioritize the most popular stuff first.
Of course, the problem was that people would get upset if something near the top hadn't been made yet. That's why I eventually took the list down. Now I just work on whatever I feel like making that day, instead of chasing the votes. So yeah, maybe it's selfish... but at least I'm having fun.
And I think my videos are better if I'm having fun. You can definitely tell when I'm recording something I don't care as much about. :)
Thomas Gonder
@Reply 9 months ago
GDPR?!!! Now I've got to go look that up and add it in.
As much as I would like to see The List, I would rather see you work on whatever has your curiosity piqued on any given day. Whether you read an article about or had an idea for a new approach to an old problem, I agree that we benefit from your engagement with the topics.
If I knew that The List just creates headaches, I probably wouldn't post it. If I wanted to create conversation, I might post it, in random order, and elicit comments about topic interest and application from members.
Matt yeah, that seems to work best for me. Posting The List made more sense when I had to worry about paying the mortgage every month and had to chase dollars by doing what was most popular (ehem... Photoshop). Fortunately now I have a little more freedom because I have an awesome subscriber base of loyal Access lovers. Love you guys.
Michael yeah, I don't know why they'd do that. It only makes the text less searchable... less findable. Again, I'm not going to pick on a specific politician here, but I will criticize policies, and this policy makes no sense.
Sorry, only students may add comments.
Click here for more
information on how you can set up an account.
If you are a Visitor, go ahead and post your reply as a
new comment, and we'll move it here for you
once it's approved. Be sure to use the same name and email address.
This thread is now CLOSED. If you wish to comment, start a NEW discussion in
Captain's Log.