Why Zero is Often the Wrong Default Value Setting

In this video, we'll talk about why using zero as a default value when designing tables in Microsoft Access can often lead to bad data and misleading results, and why it's better to use null values. We'll also cover where the fitness database series is headed, focusing on tracking body composition, the basics of building new tables from scratch, choosing fields and data types, atomic data structure, and organizing your data for more useful charts and queries. Even if you aren't interested in fitness, the techniques shown can be applied to any Microsoft Access database project. This is lesson 66.

Members

There is no extended cut, but here is the file download:

•  File Download - Gold Members

Silver Members and up get access to view Extended Cut videos, when available. Gold Members can download the files from class plus get access to the Code Vault. If you're not a member, Join Today!

Prerequisites

• Fitness, Part 65

Recommended Courses

• Access Developer Courses

Up Next

• Fitness, Part 67

Learn More FREE Access Beginner Level 1 FREE Access Quick Start in 30 Minutes Access Level 2 for just $1 Free Templates TechHelp Free Templates Blank Template Contact Management Order Entry & Invoicing More Access Templates

Resources Diamond Sponsors - Information on our Sponsors Mailing List - Get emails when new videos released Consulting - Need help with your database Tip Jar - Your tips are graciously accepted Merch Store - Get your swag here! Questions? Please feel free to post your questions or comments below or post them in the Forums.

Keywords

TechHelp Access, zero is often the wrong default value, default null vs zero, table design best practices, body composition tracking, fitness database series, body fat percentage calculation, tracking fat mass and lean mass, blood pressure fields, BMR, visceral fat, resting heart rate, Excel data staging, data import tips, atomic data fields, avoiding bad data, charting trends