I have a table for Customers and a table for Jobs (one to many)

One layout, "Today" shows any jobs that have today's date and the Summary Field gives me an accurate total of the jobs for the day.

Price and SummaryPrice are fields in the Jobs table.

Another layout, "Pending" gives me all the jobs that have not been completed (in the future, hopefully) and yet the same Summary field only shows the "total" of one job. As I click down the list, the Summary changes to reflect only the one I click on.

I use a script attached to a button to take me to each layout and perform the search. I'll attach images of my scripts and the Summary field itself used in both layouts.

The only key difference I see is that one is a layout of the Customer table, while the other is a layout of the Jobs table, while both show fields from both tables.

If you have a summary field in the Jobs table and you have placed it on a layout of Customers, it will show the total of customer's jobs - ignoring any found set.

Can I just recreate that same layout, but choose the other table as the base, while just putting the exact same fields in?

ETA: I just pulled up the Manage Layouts and changed the "associated table" of the offending layout to the Jobs table and now the Summary field works like a champ.

Interesting.

I'm not sure what you're after.

Not sure how to explain it better.

In one layout (based on Jobs) I pull up a list of jobs for today, and I'd like a total for the day (from the Jobs::Price field)

In another layout (based on Customers) I pull up a list of jobs in the future and I'd also like a total of jobs booked from the same Price field.

Trouble was, if I wanted the summary of the Jobs::Price field to be accurate, I needed to make sure they layouts were "associated" with the Jobs table, even though they look identical and feature fields from both tables.

Switching the associated table to "Jobs" for both made them both work correctly.

Well, you can't have a list of jobs on a layout of Customers - unless it's a list of related jobs in a portal.

I don't see why you need two identical layouts of the Jobs table, instead of just performing a different find using the same layout.

The one for pending is more of a list format just giving a hint of what is coming up (typically 20 +jobs) and a way to see them all at a glance.

While the one for "today" is much more detailed with all the notes, directions, times, employees and such needed so a manager has one sheet showing him what is needed for that particular day.

As to your statement about needing a portal to show related jobs, that isn't consistent with my experience. I based it on Customers and pulled up all the jobs that I was looking for, searching for their dates. Flipping the "associated" table didn't affect the body of my layout one bit. I have individual fields from Customer and from Jobs right there, no portal.