Yep, you've put your finger on the key issue. Assuming that Trades, Units and Log Entries are separate tables, this report is difficult to create in FileMaker.
If the report had just Units or Just Log Entries, you could base the report on that table and pull data from Trades to insert into headers or Sub Summaries. If the tables had this structure: Trades---<Table1 ---< Table 2, you could base the report on Table 2 and pull data as needed from Table 1 and Trades into those same layout parts, but you appear to have Units>---Trades---<Log Entries and that's a problem here.
To do this in FileMaker you have two options--both are problematic here:
Base the report on Trades and place two portals in the body, one to Units and one to Log Entries. Make these portals many rows tall and set them to "slide up, also resize enclosing part". Since these portals can be set to shrink but not grow there's always the potential problem that you may not have made a portal tall enough--plus portals that cross a page break don't always break "cleanly" in FileMaker 11.
Define a merged "report" table that combines the needed fields for both Units and Log Entries and import data into this table each time you need the report. You then have to either create calculation fields that selectively display values depending on whether a given record is a Unit or Log record with other fields or conditionally formatted text that selectively display the appropriate field labels. Often, you end up layering fields and conditionally formatted layout text on top of each other. (Such layout text must use a drastic text size change to "disappear" for fields where they aren't needed.)
Thanks for the quick response and for the suggestions. I had been using the portal approach, but I thought there might be something better.
I have to admit, I'm a bit surprised that something so basic is so difficult to do in FileMaker. Two follow-up questions: (1) Are there any third-party add-ons that add reporting features like I need? (2) Is the FileMaker team planning on beefing up this (IMHO tremendously glaring lack of) functionality?
While I'm at it, I'd like to throw out a few more suggestions having come at FileMaker from a pretty long career of using other database tools: (1) Enable/disable, show/hide fields and other objects on layouts. (2) Object orientation. In other words, layouts=objects, fields=objects, etc. Every object has properties and methods. (3) "Unbound" fields/controls on forms. Something like your "merge fields" but they are calculated fields that are not necessarily bound to any particular field in a table.
I can't say I entirely dislike using FileMaker, but I'm coming to understand that to master it you have to keep track of a long list of "arcane" features and work-arounds. I just wish that needed features were more directly implemented in the product. Suggestion #1, above, is a perfect example.
Thanks again for your help.