https://en.wikipedia.org/wiki/Database_normalization https://en.wikipedia.org/wiki/Database_normalization You find that database armatures usually store everyt

https://en.wikipedia.org/wiki/Database_normalization https://en.wikipedia.org/wiki/Database_normalization You find that database armatures usually store everything in one table. The professionals break things up into different tables using normalization. For example you usually have a table with names in it and an ID, and then you have a transaction table that has the ID in it plus the transaction with a foreign key going back to the table with names in it. Could be names of each account or checking or savings account with an ID assigned to them. Thing is you could be downloading more than one account and you don't want them mixed up into one CSV file. You want them separate in normalized tables. Now you could just have a CSV file with Account ID in it and then have a separate CSV file with the name of the account with the ID in it. But that just gets confusing. What if you are a business and have several accounts you want to download and process? You don't want them all mixed up together. Yeah there could be sub-accounts as well that have an ID as a foreign key and then another Foreign key to the main account or sub-sub account etc. When you get into accounting and you have sub accounts and sub-sub accounts to track spending you have to have a way to figure out how they work. Here is an example of tables with sub accounts: http://www.utteraccess.com/forum/lofiversion/index.php/t1855469.html http://www.utteraccess.com/forum/lofiversion/index.php/t1855...