You might have the right table structure. You want to create a summary field using the max function on record ID to determine the most recent forecast - then push that field back to the child table as a lookup. Create a formula checkbox that compares the lookup field to the record ID; if they equal, you have the most recent forecast record.
You might need 3 tables:
1.Parent-parent where key field is item
2. Parent where key field is YYYYMM|item
3. Child where key field is record ID.
Table 1 is your item master
Table 2 contains the most recent forecast in any given month
Table 3 contains all forecasts
You�ll want to use global app variables to automate the switching between months (since most forecasting processes are either 12 month forward rolling or fiscal year based)
Lastly, you have the alternative of using Quickbase actions for record keeping purposes. Your table 3 would be populated by Quickbase action, and the user would enter data in table 2. (You could avoid the goofy circular lookup method described earlier)
This is high level but I�ve built a boatload of forecasting apps in Quickbase- if this didn�t help, clarify and I�ll see what I can do.
