formula to total then divide field
I have what seems like should be an "easy" problem to fix. I just cannot figure it out. But I know someone has ran into it before so I reach out to the oh-so intelligent community :) I have a sum...
Forum Discussion
I see two solutions.
Why don't you load up a table with all the weeks for the next 10 years and all the months for the next 10 years and all the days for the next 10 years.
Then make your summary totals and make pretty charts or summary reports.
The second solution is to have a control record, which in its simplest form if there are few concurrent users is just a single record in a table which is record ID# = 1 and make that related to all details record. The the user edits that records for the start and end date. Those dates flow down to the detail records and are used in he Summary fields which do the totals back up to your control record.
So if the users need to see trends over time they look at the pretty charts or less pretty summary tables. If they need a specific date range they enter those dates.
There is also a way to do this so users don't trip over each other if there are many concurrent users setting the date range on that single control record.
Why don't you load up a table with all the weeks for the next 10 years and all the months for the next 10 years and all the days for the next 10 years.
Then make your summary totals and make pretty charts or summary reports.
The second solution is to have a control record, which in its simplest form if there are few concurrent users is just a single record in a table which is record ID# = 1 and make that related to all details record. The the user edits that records for the start and end date. Those dates flow down to the detail records and are used in he Summary fields which do the totals back up to your control record.
So if the users need to see trends over time they look at the pretty charts or less pretty summary tables. If they need a specific date range they enter those dates.
There is also a way to do this so users don't trip over each other if there are many concurrent users setting the date range on that single control record.