Portal Filtering only limits what is visible in the portal -- not the underlying related records. Thus the calculation will return exacly the same results whether or not the portal is filtered.
You need to set up actual relationships which use the data range as part of the relationship match criteria. You this will mean that if the global date fields are not entered, that set of relationships probabaly won't return anything.
For that reason, your calculation will need to be revised as a Case statement to pull the current relationship Sum if one or both dates for filtering are blank, but to use the sum across the date-limited relationships if both dates are filled in.
You cannot rely on portal filtering alone to control a sum via the relationship.
Thanks Stephen I will give thata try.
Another question. I cant seem to filter the relationship by using a global date range. I am using a start date and an end date and comparing it to a creation date of the Employee line item. No matter how I set this up it will not show any records in the portal when the date filter is in place in the relationship. Once I remove the date filters the REG Time relationship filter works fine. If any one could provide some advice i would appreciate it. I learned about this in the Filemaker trainin module but cant seem to get it to work in this application. See the screen shots below of my setup.