Thank you for your post.
The method you know (12 additional fields) is fine. However, since your pop-up field is already set to take values from another table, create a relationship between the current table and the value list table, and link the two tables together using the pop-up field. Next, in the value list table, create a calculation field with the formula:
Count ( OriginalTable::Popup )
This will then extract the number of times the pop-up value has been used in the other table. You can then use the values from the calculation field to perform the charting.
Let me know if you need additional clarification.
If you are adept at SQL, you may be able to use the new ExecuteSQL function in FMP 12 to set variables with the counts without creating new fields
ExecuteSQL("SELECT COUNT(…) FROM … WHERE …";"";"")
Thank you - I am using a value-list not a table for the pop-up. But the answer still works where I can either change to using a table for the value-list
Or just create a new table (with same values in the Key field as value-list). - I suspect option one is what you would recommend (no duplication of the data) . So that is the way I will go..
Either way the count on relationship was the trick i had not figured out.
Also thanks to Jade - still a better method than the original. A lot of the charting examples I have been looking at do use SQL calls - Guess it depends if you want the chart data in a lot of variables or into a table. I think when you start to get a lot of Non numeric type data to chart EG more fields - for me I think I prefer a table for each field.(the chart then will be easier I think) Probably just personal preference... Or could just be how much programing background I have/havenot had ?
Anyway Both are Much better than fileds all over the place !