Computer Learning Zone CLZ Access Excel Word Windows

Strength does not come from winning. Your struggles develop your strengths. When you go through hardships and decide not to surrender, that is strength.

-Arnold Schwarzenegger
 
Home   Courses   TechHelp   Forums   Help   Contact   Merch   Join   Order   Logon  
 
Back to Captain's Log    Comments List
Upload Images   @Reply   Bookmark    Link   Email   Next Unseen 
Why Null Is Better: A 150-Year Old Mistake
Richard Rost 
          
13 months ago
This morning, while sipping my Raktajino, I reviewed President Trump's recent address to Congress. He claimed that millions of centenarians - some purportedly as old as 150 - are receiving Social Security benefits. Let's discuss...

First of all, this is not a political post. I try to avoid bringing politics into my teaching whenever possible because I do not want to alienate anyone. Mistakes like this can happen no matter which party is in charge. This is not about Democrats or Republicans. This is a database post.

The real story here is not fraud or corruption. It is a database design problem.

These ridiculous birthdates are the result of placeholder values used in the system. When the Social Security Administration does not have a date of birth for someone, instead of leaving it blank, they used a placeholder date. One commonly used is May 20, 1875. This goes back to an old ISO 8601 convention that, for unknown dates, systems would use a specific value as a filler. So now, when they pull up records, it looks like there are people who are 150 years old still collecting benefits.

This is not a good practice. As any of you who follow my lessons know, I am a big fan of leaving unknown values as null in Microsoft Access databases. Null means "I do not know." It is much better to leave a date field null than to use something like 1/1/1900 or some other fake value. That way, when you run reports, you can clearly filter out the unknowns. You do not end up with crazy data making it look like someone is still cashing checks from the Rutherford B. Hayes administration.

And before you ask, "what happens if I have to perform calculations on a null date?" The answer is: you handle it. You check for nulls in your queries and formulas. That is much cleaner than filling your table with bad data just to avoid nulls. Remember what I said way back in Access Beginner 1: "NO data is better than BAD data." That's data with a lowercase "d." We don't need crazy androids causing mischief.

So the real lesson here is this. If the Social Security Administration had used nulls instead of placeholder dates, we would not have 150-year-old people throwing off the reports. This is why good database design matters.

Your thoughts?

Live long and prosper.
RR
Richard Rost OP  @Reply  
          
13 months ago

Sami Shamma  @Reply  
             
13 months ago
It is hard to reply without sounding political. So, I will do what my teacher has done and stick to database issues. absolutely NO data is better than BAD data. I have been practicing that ever since you said it in biggner 1.

I had a problem not long ago (about 6 weeks) where imported data from the 54-year-old mainframe contained Null that was not handled in my code. it caused a problem that took me days to figure out. now, I NZ the daylights out my code just in case.
Matt Hall  @Reply  
          
13 months ago
I work with measurement devices in industry.  To me, a failed device is always preferable to one that just reads wrong.  The failed device prompts corrective action.  The one that is reading wrong goes unnoticed, sometimes for years.  Its a very similar situation.

Richard Rost OP  @Reply  
          
13 months ago
Then again... Sometimes giving a faulty reading is actually a good thing. There was an incident with the Space Shuttle where one of the engines had a problem and was burning either too much or too little fuel. Under normal conditions, this would have been a serious issue, but one of the sensors that was supposed to monitor it failed and gave a bad reading. Ironically, that incorrect data caused the system to make adjustments that ended up correcting the fuel problem. If the sensor had worked properly, the issue might not have been fixed, and the mission could have been in danger. It is a rare example of how bad data can sometimes save the day.
Richard Rost OP  @Reply  
          
13 months ago
I had to look it up because I couldn't remember the details...

It seems you're recalling an incident involving the Space Shuttle's engine fuel consumption and a sensor malfunction. One notable event that fits this description is the launch of STS-93 in 1999. During this mission, the Space Shuttle Columbia experienced a hydrogen leak in one of its main engines due to a damaged component. This leak caused the engine to consume more oxidizer than expected. Simultaneously, an electrical short disabled the primary controller of the center engine and the backup controller of the right engine. Despite these issues, the shuttle's systems compensated for the anomalies, allowing the mission to proceed safely.

Thomas Gonder  @Reply  
      
13 months ago
I saw this claim (SS payments) about two weeks ago on FB. My critical thinking went a bit off idle. How can the SSA send payments to someone they don't know, and have verified, the birthdate of?

I'm waiting until 70 to make my claim, just because I want to procrastinate the giant headache I know is coming. I went through this with my mother, good grief, it was a pain.
Sami Shamma  @Reply  
             
13 months ago
One trip to the SS office in Hartford CT, and my payments started on time. I have nothing but good things to say about the process.
Matt Hall  @Reply  
          
13 months ago
What if you are one of the people that was eligible 80 years ago?
Joe Holland  @Reply  
      
13 months ago
Sing it from the hill tops. Don't make up data when you don't know it. Leave it blank and fill it in later if/when you have the data.
Thomas Gonder  @Reply  
      
13 months ago
@Joe And don't make it a required field if it's possible that the user might have reason to not know the data.
Seen my Fred Flintstone demo on YouTube? Fred creates a record for James Bond, with just those two pieces of data. Heck, the last name isn't even required.  Compare that to websites that refuse to do anything without a ton of impossible fields filled in.
Joe Holland  @Reply  
      
13 months ago
A little thinking ahead would go a long way with some of these websites. I watched your Fred Flintstone demo, but it was a while back.
Thomas Gonder  @Reply  
      
13 months ago
@Joe The other day I was trying to make a purchase from a company in the USA, to be sent to Colombia. The site wouldn't let me enter a non-USA phone number, but did have a country field for the address, which showed Colombia in the drop-down list. I couldn't "Pay" without a valid phone number. Doh!

Thanks for watching Fred. Yabba Dabba Doo.
Sandra Truax  @Reply  
         
13 months ago
I agree with Sami, one finally bad day at work with the new Warden, went to my office, contact SS about what I could draw off my husband who had passed the year before, by the end of the day I realized I could draw as much sitting at home drawing retirement and SS as I was making going to work every day. Turned in my resignation the next day. But then again, it probably helped that I had an inside contact that I delt with to make sure inmates SS payments were stopped while incarcerated.
John Davy  @Reply  
         
13 months ago
I think I was born on May 20, 1875 and still want my SS check  John

This thread is now CLOSED. If you wish to comment, start a NEW discussion in Captain's Log.
 

Next Unseen

 
New Feature: Comment Live View
 
 

The following is a paid advertisement
Computer Learning Zone is not responsible for any content shown or offers made by these ads.
 

Learn
 
Access - index
Excel - index
Word - index
Windows - index
PowerPoint - index
Photoshop - index
Visual Basic - index
ASP - index
Seminars
More...
Customers
 
Login
My Account
My Courses
Lost Password
Memberships
Student Databases
Change Email
Info
 
Latest News
New Releases
User Forums
Topic Glossary
Tips & Tricks
Search The Site
Code Vault
Collapse Menus
Help
 
Customer Support
Web Site Tour
FAQs
TechHelp
Consulting Services
About
 
Background
Testimonials
Jobs
Affiliate Program
Richard Rost
Free Lessons
Mailing List
PCResale.NET
Order
 
Video Tutorials
Handbooks
Memberships
Learning Connection
Idiot's Guide to Excel
Volume Discounts
Payment Info
Shipping
Terms of Sale
Contact
 
Contact Info
Support Policy
Mailing Address
Phone Number
Fax Number
Course Survey
Email Richard
[email protected]
Blog RSS Feed    YouTube Channel

LinkedIn
Copyright 2026 by Computer Learning Zone, Amicron, and Richard Rost. All Rights Reserved. Current Time: 4/30/2026 10:51:40 AM. PLT: 1s