efficiency

[The Dummy in Access for Dummies]

In regards to efficiency, is it better to have one query table with all of
the calculations in it, or to separate each calculation in a different query
table?

 

[mscertified]

what do you mean by 'query table'?

 

[The Dummy in Access for Dummies]

Is it better to have all of the calculations in one calculated query or
should I have create a calculated query for each calculation? Query table; I
mean like having the sum of a series of fields and the standard deviation of
the same series of fields in the same query design? (keep in mind that this
is just a simple example, I actually have quite a number of calculations)

 

[The Dummy in Access for Dummies]

Is it better to have all of the calculations in one calculated query or
should I have create a calculated query for each calculation? Query table; I
mean like having the sum of a series of fields and the standard deviation of
the same series of fields in the same query design? (keep in mind that this
is just a simple example, I actually have quite a number of calculations)

 

[The Dummy in Access for Dummies]

Is it better to have all of the calculations in one calculated query or
should I have create a calculated query for each calculation? Query table; I
mean like having the sum of a series of fields and the standard deviation of
the same series of fields in the same query design? (keep in mind that this
is just a simple example, I actually have quite a number of calculations)

 

[Smartin]

I suppose it depends on how you define "efficient". In one sense, it
would be more efficient to do all the calculations in one query, so as
to avoid writing multiple queries, and possibly the work entailed in
stitching the correlated results together again later.

On the other hand, I have no idea. Is it more efficient from a processor
POV to run multiple calculation queries versus one query with a bunch of
calculations?

You could test this using VBA to time each method over several trials.
But, I suspect (with absolutely no reason to other than intuition) if
the number of records is relatively small (say, 1000s, not 1000000s) the
difference will be negligible on modern equipment.

 

[The Dummy in Access for Dummies]

Thanks anyway.

I suppose it depends on how you define "efficient". In one sense, it
would be more efficient to do all the calculations in one query, so as
to avoid writing multiple queries, and possibly the work entailed in
stitching the correlated results together again later.

On the other hand, I have no idea. Is it more efficient from a processor
POV to run multiple calculation queries versus one query with a bunch of
calculations?

You could test this using VBA to time each method over several trials.
But, I suspect (with absolutely no reason to other than intuition) if
the number of records is relatively small (say, 1000s, not 1000000s) the
difference will be negligible on modern equipment.