Had a look at your db. Sorry to say you are doomed to experience a few serious problems and probably many more not so serious. At first glance, you have all sorts of special characters in your object names (even starting a name with a dollar sign) and plenty of spaces, tables with many duplicate rows, comma separated values in fields, many-to-many relationships between what should be one-to-many ([Dealers].[Corporation #] to [Raw Data].[Corp No]), query field references for what looks like non-existent fields (SumOfDura-lift: Sum([Monthly Summary By Category - Step 1].[Dura-lift]) (I see no Dura-Lift field in that query) AND every field in the detail section of your report has an invalid data reference. The last issue is probably why your report wants the date 3x. Each query that calls an underlying query uses the same field name, which may be why Access cannot resolve the field reference in your report. It says it's an invalid reference even though the field exists (but 3 times, once at each query level) and it does not show up in the list of available fields for the control (based on the report's data source). When I tried to use the builder to see how/if it would find the field, the db crashed. So if this is an issue for the company data field, it certainly could be for the date being supplied.
With all due respect, you have some serious design issues.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.