I have large database containing thousands of records which I am required to query on a weekly basis. I then have to create summaries of this data using Access Reports. When I first created the database (which I did very recently), I built several types of queries (about 80) and then created subreports off each, and then put these sub reports in one giant main report.
I have never used a database before and something tells me that maybe I shouldn’t have 80 different queries, populating 80 different subreports. I don’t know, maybe it’s okay. But that’s my question, is there any reason why I should go back and redo some of these queries and consolidate them into maybe 20 or 30 (which would require me to redo the sub reports and the main reports), or is it perfectly fine to have this many queries saved in my database.
Keep in mind, each query, though containing only 2 or 3 functions each, has a very specific task that I cannot get rid of completely, I would only be able to add these functions into a larger query by combining several types of queries. Also, like I said, I have to use these queries on a weekly basis, so I don’t really want to build them on the fly like some people choose to do.
Anyways, is there some unforeseeable problem that I am missing with having this many queries, or is this normal?
If it performs to your requirements (i.e. it’s “fast enough”) and doesn’t hinder others (i.e. it doesn’t slow everyone else down), then it should be fine.
I would just make sure that all of the queries run well individually against your target data set. It may run great against 50 rows in development, but you have 1M rows in production.
But if it runs fast enough for you on your production DB, then be done with it and go solve another problem.
If you want to take a learning experience from this, then apply it on a future project rather than repaving a road you’ve just laid.