"Normalized" is a database term (among other disciplines) that describes a particular style of laying a table and its contents. It is a way of gathering things together to keep "like" with "like" and to separate the things that are not like each other. Once you understand it, database normalization is a way to save space AND save effort.
Thinking back on your questions that I have seen in the past, I realize that part of your problem is continually thinking along what we call "flat-file" lines. A spreadsheet is a flat file in which you list data in a grid. But sometimes your data has an inherent structure. A spreadsheet - Excel or any other brand-name - has really no easy way to efficiently represent hierarchies or parent/child structures. The table you showed us has what is called a "repeating group" which is one big indicator of normalization issues.
For instance, you show table Investments01K_tbl with fields such as BMO_Intel_02, CFRA_Advc_02, MRNG_Advc_02, .... BMO_Intel_03, ...., BMO_Intel_04, etc. That should be TWO tables... Investments01K_tbl and a child table with a field showing BMO_Intel, CFRA_Advc, MRNG_Advc, ... plus some field that links it back to the specific record in Investments01K_tbl. Flattening out those items into the single table causes you have to write extra code for each of the _02, _03, and _04 columns. Not to mention the headaches that would be caused by needing to add a 5th column.
I know you folks work by committee and are volunteers but let me say that you will ALL work a LOT less if you learn to normalize your databases. You can search this forum for keyword "normalize" because this IS a database forum. However, if you really wanted to study this, search the general web for "Database Normalization." You need the "Database" as a qualifier for web searches because "normalization" also is used in the fields of mathematics, chemistry, medicine, physics, and international diplomacy. At least at first, pick articles from .EDU sites - but don't ignore the .COM sites that have explanations of normalization. Just realize that they might have something they waht to sell to you.
If you do some reading on the subject, you might see WHY you will work less down the road. This is DEFINITELY a case of "pay me now or pay me later" when designing a database, and trust me this much: The later you wait, the more you will have to pay.