Dan:
Thanks for the feedback...
I understand this issue about attachment... so, let me try to put the
"picture" into words.
This is what I currently need to achieve/work on:
- I work on a Balanced Scorecard prototype db
- I want a single form with lots of small "boxes" (textfields)
- Each textfield (I might have 200 or so) will store a value which value
"drives" the color of the textbox. For instance, if the value = 100 (100%)
then the background color is green. If it's e.g. "25", it'll be red.
- In the end, I simply want to be able to click on a "red box" and see the
underlying data (25% plus other fields that describe "why it's only 25% such
as missed deadlines, resource constraints, etc.").
The last bullet is the challenge I'm trying to solve at this time. "Click
on a texfield" and bring up a query/subform/report that shows the source
data".
Lastly, I kinda have had my concerns about the normalization problem myself.
You're absoulutely right, it might become a nightmare to maintain hundreds
of textfields (specifically, as they will be pulled in queries and linked to
forms).
Based on the information I have shared w/ you, would you mind sharing some
more insights w/ me as to how I can best design the table structure.
Essentially, I need to be able to store data about
Task 1.1
Task 1.2
Task 1.2.1.
Task 1.3
....
....
Task 200.1
....
etc.
Looking forward to any pointers you might be willing to share w/ me.
Tom