In order to reduce the runtime of some Access reports I am populating a table with query data and having the report pull from that table. The two steps to the process are
1) Removing the old data/deleting the old table.
2) Populating emptied tables and building new tables.
This has reduced the runtime of my reports by a factor of 5 (over just having them pull from the queries). Unfortunately, everytime a report is run the database increases in size by about 2 megs. Our staff knows enough to run compact and repair every now and then, but I'm fairly certain that our client (social workers who know nothing about computers) would be flabbergasted at the concept and inconvenience. Is there anyway that I can either prevent Access from saving all that unnecessary table changing or perform an automated 'compact and repair' from time to time?
1) Removing the old data/deleting the old table.
2) Populating emptied tables and building new tables.
This has reduced the runtime of my reports by a factor of 5 (over just having them pull from the queries). Unfortunately, everytime a report is run the database increases in size by about 2 megs. Our staff knows enough to run compact and repair every now and then, but I'm fairly certain that our client (social workers who know nothing about computers) would be flabbergasted at the concept and inconvenience. Is there anyway that I can either prevent Access from saving all that unnecessary table changing or perform an automated 'compact and repair' from time to time?