Common Sense and Why Atomic Fields Are the Foundation of Useful Data

In January 1776, Thomas Paine published Common Sense — a pamphlet that spread through the colonies like wildfire and helped galvanize public opinion toward independence. Paine was a meticulous communicator. Now imagine he kept a subscriber list in a notebook with entries like this:

Now suppose Paine needs to send the next issue only to subscribers in the Massachusetts Colony — sorted by city, then by street. With every name and address crammed into a single field, that task is nearly impossible. There is no way to reliably sort or filter data that is all jammed together in one column.

This is the fundamental problem that atomic fields solve. In database design — whether you are working in SQL Server, Microsoft Access, or even a well-structured Excel table — an atomic field holds exactly one piece of information. No more, no less. Name, colony, city, and street address each belong in their own dedicated column.

Identify and separate combined fields in your data

1. Look at each field (column) in your table and ask: "Does this field contain more than one type of information?" A field like FullName or FullAddress almost always does.
2. Split combined fields into their smallest meaningful parts. A name field becomes FirstName and LastName. An address field becomes StreetNumber, StreetName, City, Colony (or State), and PostalCode.
3. In SQL Server or Access, create separate columns for each atomic value. In Excel, use the Text to Columns feature (Data tab → Text to Columns) to split existing combined data into separate columns automatically.

Apply atomic design when building new tables from scratch

1. Before creating any table, list every question you will ever want to ask of this data. "Which subscribers live in Massachusetts?" "How many are in Boston specifically?" "Who lives on King Street?" Each question implies a separate field.
2. Give each field a clear, single-purpose name. If you find yourself using "and" or "/" in a field name — like City/Colony or NameAndTitle — that is a sign the field needs to be split.
3. In Access or SQL Server, define the correct data type for each field (text, number, date, etc.) to ensure data is stored consistently and queried efficiently.
4. Test your design by writing a few sample queries. If you have to use string-parsing functions like LEFT(), MID(), or INSTR() to extract part of a field's value in order to answer a basic question, your data is not atomic enough.

What Paine's subscriber table should have looked like

Now Paine can instantly sort by Colony, filter by City, or pull every subscriber on a specific street — in seconds. He could even use this structured list with Word's Mail Merge to personalize every copy of Common Sense by colony. Revolutionary, indeed.

The takeaway

The principle of atomic fields is one of the most important — and most commonly overlooked — foundations of good data management. Whether your data lives in SQL Server, Access, or a carefully structured Excel table, building it right from the start will save you enormous time and frustration down the road. Just ask Thomas Paine.