You need some kind of relationship here. Will there only be one record in the Breakouts table and will it always match to all records in Main?
If so, you can set up a relationship like this:
Breakouts::anyfield X Main::anyfield
the cartesian join operator is something you can select in place of = in a relationship if you double click the line linking these two table occurrences in Manage | database | relationships.
But be advised that I wouldn't structure my breakouts table with separate fields for each expense. I'd set up a table where each expense in it is a separate record.
Thanks for the reply Phil,
Yes, there will only ever be one record in the Breakouts table, and yes it will aways match to all records in the Main table. I adjusted the relationship per your suggestion and it (so far) seems to do exactly what I needed it to do.
You suggest I restructure my Breakouts table so each expense is in its own record. What would be the advantage of doing it that way versus just in one record?
Please note that this change would also require a change in the relationships used to combine data in your two tables.
But consider what you must do if the business changes in some way and you discorver that an entirely new expense must be documented in the Breakouts table. With your current set up, you have to add a new field to your table and update any calculation fields that compute total costs.
If each expense is it's own record, such a change requires simply adding one more record--which is much simpler and does not require a Filemaker developer to do. That's just one example of the increased flexibilty possible when you put each expense in a separate record instead of using separate fields in the same record.
Thanks Phil, you bring up some good points. I'll definitely have to give the structure a little more thought.