I have a dilemma. I need my app to print out legally binding property schedules for insurance purposes. A property can have any number of schedules created during a year according to how many changes are made.
My instinct is to use a set of nested queries to generate the reports and then save them as snapshots should they need to be referred to later (they will!!).
However I have just been wondering if I should create a new table that gets populated with the full data for each property schedule when one is printed so that there is a definitive and tangible record for each schedule.
The latter seems like not good practice within Access as I know it but I have this niggling hunch that it might be the right approach for this app. On the lazier note it would also make re-creation or subsequent investigation very much easier than having a whole sequence of horribly dynamic queries!
Does anyone have anything similar (sure someone does) and what did they do?
Thanks for any input
My instinct is to use a set of nested queries to generate the reports and then save them as snapshots should they need to be referred to later (they will!!).
However I have just been wondering if I should create a new table that gets populated with the full data for each property schedule when one is printed so that there is a definitive and tangible record for each schedule.
The latter seems like not good practice within Access as I know it but I have this niggling hunch that it might be the right approach for this app. On the lazier note it would also make re-creation or subsequent investigation very much easier than having a whole sequence of horribly dynamic queries!
Does anyone have anything similar (sure someone does) and what did they do?
Thanks for any input