Ok, here's more information on the scenario;
School Counselors from schools across a county maintain demographic records (no personal info) of students at hunger risk. We deliver weekend food packs to the schools on Fridays to ensure these kids have food over the weekend (school meals often their only sure meal). The list changes unpredictably as students dome and go from schools or in and out of the program (parental permission required). The schools are in a county, the county is in a region.
On Friday morning a Datapage tabular grouping report is run to show several bits of joined information, including the count of students per school as of that Friday morning - a snapshot of the current state of the counselor's detail lists (these are RLS protected). This report is then used as guidance to a team of volunteers who deliver the count of food packs to the school on that Friday. This is still in proof of concept mode but all testing indicates this is delivering the right results and accurately reflecting the counselors' entries, deletions, edits, etc.
What I want to add is a way to capture that snapshot, with date, to a history table so that over time, totals for time periods and trends, etc,, can be reported, analyzed, etc. Don't want the counselors to have to deal with dates, status switches, etc., just maintain their simple , current list - what you see is what is real at that moment.
I have a multi-table joined view that is behind the rollup tabular Friday report that shows all the information. A way to write the history snapshot from the view would also work. Ok if it is done in the Bridge instead of web page. Just need to capture the the snapshot of the weekly delivery info into history week-to-week, with a date added (at authorized user discretion).
Thanks for responding. Hope that helps to understand. Open to different approaches that achieve same end, including a little raw SQL with some help on where and how.