B
Brad
We have multiple reports that use data from a single query. This query is
tied to another application’s tables via ODBC.
The data in the other system’s tables is being updated continuously.
Currently we run each Access 2007 report separately which in turns initiates
the underlying query for each report.
This works fine, but we are concerned that we may see different results in
the case where the data in the underlying table is changed between when
Report1 is run and when Report2 is run. (It is important that the summary
data is the same on both reports)
Is there a way to force Report2 to use the results of the query that were
built when Report1 was run?
We have started to experiment with sub-reports, by making Report2 a
sub-report of Report1. However, It appears that the underlying query is run
once for the main report and run again for the sub-report.
Thanks in advance for your help.
Brad~~~~~
tied to another application’s tables via ODBC.
The data in the other system’s tables is being updated continuously.
Currently we run each Access 2007 report separately which in turns initiates
the underlying query for each report.
This works fine, but we are concerned that we may see different results in
the case where the data in the underlying table is changed between when
Report1 is run and when Report2 is run. (It is important that the summary
data is the same on both reports)
Is there a way to force Report2 to use the results of the query that were
built when Report1 was run?
We have started to experiment with sub-reports, by making Report2 a
sub-report of Report1. However, It appears that the underlying query is run
once for the main report and run again for the sub-report.
Thanks in advance for your help.
Brad~~~~~