Is this a good table design or am I setting myself up for disaster in
the future?
I have set up two access tables: Projected and Actual. Each table has exactly the same fields, except one is projected and the other is actual (example: Revenue/Actual Revenue; Cost/Actual Cost). There are also other "identifier" fields which are the common link between the two tables such as division and initiative. Each table is pretty large- 30 fields.
Let me know your thoughts on this. Thanks!
the future?
I have set up two access tables: Projected and Actual. Each table has exactly the same fields, except one is projected and the other is actual (example: Revenue/Actual Revenue; Cost/Actual Cost). There are also other "identifier" fields which are the common link between the two tables such as division and initiative. Each table is pretty large- 30 fields.
Let me know your thoughts on this. Thanks!