Then that tells you how to make the joins for the tables: one project to many financial data items.
The financial data itself is associated at the lowest possible level (bbbb or project level in our previous example).
Actually it would be better to have all of the possible full WBS element numbers in a table and use a flag field to flag the correct one.The financial data itself contains the full WBS element number, wwww.xxxx.yyyy.zzzz in our original example as well as financial data (types and amounts as we discussed earlier). My structure in the picture is more like wwww.xxxx.yyyy.zzzz.aaaa.bbbb. Sometimes, however, this data is entered incorrectly (into the customer's other database) and when I pull the financial data (my excel import), the incorrect wbs element numbers will show up. I need to have an override table to link the incorrect wbs element numbers to an alternate corrected number.
tblOverideTable
-pkOverideID primary key, autonumber
-foreign key field to the table that holds information, I'm just not sure which table--the project table (your level 6 table???)
-txtWBS
-logCorrect (yes/no field; checked if the wbs element is the correct one, unchecked for those that are not
You would create a query that joins the incoming data table with the override table via the txtWBS field in both tables. You would select the fields from the incoming data table you want to append and the foreign key field of the override table. Change the query to an append query and select the destination table and run the append query.