Forum Discussion
Primary and Secondary tables, need help with relationship for auto create/update
Unfortunately, your description suggests an invalid, or inappropriate, table design. It sounds like you have what is often referred to as a "spreadsheet style" table, not a set of relational database tables.
Here's an excellent set of blog posts that explain the problem and offer ways to correct it.
I don't think it's a good idea, by the way, to offer you suggestions about working with this table design, even if it could be done without a wad of code.
- Thanks, I'll take a look at those threads and see what i can do! It's definitely a spreadsheet style table, mostly to have an easy data export to excel. There's simply too many values/columns for a single table, so that's why I was looking into a secondary extension.
Thanks again!
-RayRay_Barrit While it is true that tables in a normalized relational database application tend to have fewer columns in each table, that is a RESULT of the normalization process; it is not the goal in itself.
"There's simply too many values/columns for a single table" In other words, we have a principled process to reduce that number of columns. That process, called "normalization", is based on understanding RELATIONSHIPS between entities. When you do it that way, the natural outcome will be more tables with fewer fields. But, to repeat myself a bit, that's NOT the goal in and of itself.
