Sorry for the confusion, sometimes articulating these concepts can be tough! I am a big fan of yours, and solved many problems simply by reading through your answers to similar questions posted by the community. Thank you for your service, you have been a life saver to many!
Anyway, here is a little clarity:
I have a master table called Part Numbers.
I have a child table called Forecasts.
I have a third table for summary purposes called Forecast Keys.
Forecasts are predictions of how many parts might be ordered for each future month. Forecasts data for each month can change, but I never modify the record, I must always add a new record for record-keeping purposes.
For example, Part A might have several Forecast records for the same month, such as June 2018, since the outlook for June is always changing between now and then.
In order to have a field summarize the "most recent forecast" for Month X, I created a text formula field (that will serve as the reference for the third "summary" table): [Part Number]&"|"&[Month].
The only hurdle at this point was the "QuickBase does not allow summarizing relationships in which the reference is a lookup field". But after reading your post in a related discussion, I followed your advice for the workaround and the relationship and summaries work flawlessly.
However, while I can automatically create the third table's key [Part Number]&"|"&[Month] with QB action in the Forecasts table, it leaves me in a situation where, to relate/link the two tables, I would have to go into to the individual Forecast records and painstakingly record-by-record chose from the drop down the reference key that now exists in the third table.
Does this mumbo jumbo make any sense or did I just confuse you further?
