Hello Mark,
I had not had the summary field for 'field x' checked as 'treat null as zero'. I have since checked that box, but no change. Still blank values coming back for that 'summary field of 'x''.
The 'X' field does in fact have a value for 4 of the records in the table.
Thanks for the help.
With "Z", are you trying to calculate the % of Total Project that the Impact Value represents?
Yes, but... 'Total Project' is represented by 'record 1' in the table. So, yes, % of 'record 1' that the Impact Value of each other individual record represents
Qrew LegendI believe that you will need a second relationship so that all of the children are related to Record ID number one in Projects.
Try creating a field on the Child Impact Table with a formula value of 1 and create a new relationship back to the project record. Then the look up that field for that summary total down to all Impact records.
The issue is that you have a value on Project #1. But other than that special Impact record, none of the rest of your Impacts children are connected to project #rom so the lookup form Project #1 for that Total field field will be null. (which you proved!). So we make a second relationship so that every child record is attached ot that special project w/ Record ID# of 1.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
Qrew Legendnote: I edited my response above for clarity and bad dictation.
You have a Projects table and a Project Impacts table, with Projects being the Parent to Project Impacts, correct? If that is the case, then you should have Project #1 having many Project Impact records. The Project Impacts table should have a Numeric field where your users would enter the Impact Value for that particular Impact record. You would then have a Summary field for Impact Value up to the Project table. Assuming that these Impact records reflect certain expenditures for the Project, this would be "Total Project Cost". You can then create a Lookup field from the Project down to the Impacts for "Total Project Cost" so that you would now have two numeric fields on the Impact - Impact Value and Total Project Cost. You can then create a Formula Numeric field on the Impact table to calculate your % of Total Project - [Impact Value]/[Total Project Cost]
Typically speaking, when setting up your table structure, you would not want to have a record on a table represent the total of a field that is also on that same table. In your example, you have Projects and Impacts. Based on your description, you are wanting to represent the total of all Impact records on the first Impact record. This is not an ideal way to setup your application.
To properly calculate the total of a field across all records on a table, you need to have a Parent table above that and create a Summary field for the field you want the total of.
Blake, Yes, thanks, I understand. Ideally we would have set up the app as you described. However, we are trying to achieve this additionally functionality in an already existing app, and what I described above will be repeated for 4 business divisions, which is the real problem. So, ideally we would have a 'divisions' table, followed by the tables you described. We could go back and do that now, but then we'll have to re-do all the reports. So, this is why I was trying to doing it by adding a 'project' that represented total impact (revenue) for the division. Everything works doing it in this workaround fashion, except for the problem I described.
