The Relational Database structure has a certain elegance about it. When performing data modelling, you do not want to run into a many to many relationship. Thankfully, in my 20 years of building databases for businesses of all types, I never ran into a relationship I couldn’t tame.
Most every collection of data can be defined by a group of one to many structures. There most often exists a hierarchy between two related tables. It could be a quotation header record linking to several detail records, or perhaps an inventory item linked to several storage locations.
One to one relationships are possible, but can soon break down. Just throw a timestamp into the mix and you have one to many again.
The point, is that systems with such hierarchical relationships are expandable, and therefore beat the good old spreadsheet hands down. Large databases, on a server, or now in the Cloud, need to be faster, and they are.
These aren’t complicated, just different for the uninitiated. I can design it for you. Once you see it in action, you won’t know how you ever ran your small business, or big hobby, without it!