Don't you need one more table, a "programs" table where each program that you offer is listed in separate records? (Maybe that's the Accounts table, but I'm reading that as the table where you manage payment info...)
It's not just a matter of tables, but also in how you use table occurrences to relate them to each other:
Orders----<OrderItems>-----Programs ( ---< "means one to many" )
which, with different names, is the same structure you see in the Invoices starter solution that comes with FileMaker.
Beyond that, you'll need to add a submissions table where you log the receipt of each submitted name. This record can log the date, submitted name and any other data about that submission that you need.
If you can set up data entry for Submissions so that if a customer does not submit a name in November, but submits one in December, it is logged as a late submission for November, then you can more easily set up a report by searching a date field in the submissions table but from the OrderItems table. (Find all OrderItems where the date of last submission is less than the first of this month. for one example.)
Thank you very much as usual! again!
I do have the table called "winners" in which is like the "submissions" table you have mentioned. In there, I have the fields:
- _kf_orderItemsTitles <- related
Here is also the overlook of tables:
How would filemaker know if a customer submits the name in October but skips in December? I would like the system to be able to flag that so that our customer service rep can followup on that customer.