I think that for your letter you need to summarize by vendor first, then by project. So your layout could be:
[sub-summary by Vendor] Congratulations <<Vendor_Name>> you spent* <<Total_Billed>> on the following projects:
[sub-summary by Project] • <<Project_Name at <<Project Address>>
Not related to your question, but you should base your relationships on IDs (auto-entered serial numbers), not on names. Names can change, and you do not want your relationships to break when that happens. Also, it would be useful to have a Vendors table with one unique record for each vendor - so that your "Table 2" would become a table of Billings with fields for:
(*) Spent? Weren't they PAID these amounts?
Ahh! paradigm shift. Thank you.
You are correct in your assertions. The sample sentence I provided would be better structured as you stated.
In this case I am not actually creating a database application that will be long lived. Rather I am cleaning up large amounts of data (that is in pretty bad shape). The end goal is to send out lien waivers for a subset of projects. This is a one time exercise and then the database has served its purpose. I normally do this for clients on SQL Server or Access, but in this case the client is on Mac, has file maker pro and I thought I would experiment with it. Nice app. Once you move away from the query mindset the app is really easy to use and learn. In fact I think I am going to add it to my arsenal.
Thanks for your help