Performance Maximization

[james28]

Hello All,




As I start to build out my reporting and queries, I wanted to know what the best way to create queries was. Although it likely is applicable to all version of Access, I am using 2010.



I only have 1 table, but the table will eventually have 10k+ rows.



In terms of objects, I have a single report with a dozen or so charts. The charts are all based off of 1 column in my table. In order to filter out the correct information, I sort everything by a date column. By that I mean, in order to make one complete chart from a query, I ultimately need 2 columns.



My options, as far as I can tell are to go one of two ways.


Option 1:
12 Queries. Each query pulling 2 columns. The first being the date column, which will be the same across all 12 queries. The second being a column that is unique to each query.


Option 2:
1 Large query pulling 13 columns. The query would be made up of 1 Date column and then the 12 unique columns mentioned before.




From a performance stand point which is better?



Thanks!

[June7]

I don't think performance is different but I prefer to create fewer objects.

[james28]

June,

Originally, I was using a bunch of small queries, but I will try to condense them as much as possible. Thank you for the input!