Your summary field is evaluating as it is designed to do so, just not as you want it to.
If you set up this report in a layout based on the line items table, your grand total would compute correctly. Summary fields from related tables compute a value based on the set of related records, not your current layout's found set. Put a field, any field--not just summary fields from a related table into a trailing grand summary or a footer and you will see data based on the values in the last record in your found set.
You can also define a calculation field in Jobs that computes the total of each set of related line items. Then a summary field defined in jobs will compute your grand total. Such a calculation can use the sum function or it can consist solely of the name of the related table's summary field.
Yeah I got ya. I was hoping to summarize by each job, versus showing all the line items for each job... however, doing it that way does give me more granularity in reporting (we sometimes ship parts of jobs and bill out, so we could bill out that item on it's own). I'm gonna go with it for now and see how far I can take it. Thanks!
all the methods that I described permit you to "summarize by each job". If you base your report on the lineitems table, you can use a sub summary layout part with the summary field placed in it to show the sub total for that job. This requires sorting your line item records to group them by job. And you can choose to only list the subtotals without the individual line items being listed if you remove the body layout part from such a layout.
PERFECT. That's what I was looking for. So all along I should have been using a sub field instead of the body. Thanks!