E
ElPresidente
Hi everyone,
Still learning the ropes with Access so bear with me. I'm creating a
report which right now has 4 graphs on it. Each graph runs it's own
query (which I have a feeling isn't the correct way of doing this). So
when the report loads, the wait time is multiplied by 4. Would it be
better to have one large query run for the report and have the graphs
pull information from there or should I break it down into separate
smaller queries? Basically it's the overhead in days from each
department. So I could either make one query for each department, or
pull all 4 at the same time. I was thinking that doing the latter when
the report opens and basing all the graphs off that data would be the
best, but I don't know how to do that.
The other problem is that the reports have to break our data down on
either a weekly or monthly basis. There are thousands of records per
year which the query right now groups using DateDiff. I'm also
thinking about adding another table or column which will permanently
store the week number instead of having to compute it in a query. The
performance isn't bad when the database is local on my desktop, but
over the shared network it becomes a problem.
Thanks
Still learning the ropes with Access so bear with me. I'm creating a
report which right now has 4 graphs on it. Each graph runs it's own
query (which I have a feeling isn't the correct way of doing this). So
when the report loads, the wait time is multiplied by 4. Would it be
better to have one large query run for the report and have the graphs
pull information from there or should I break it down into separate
smaller queries? Basically it's the overhead in days from each
department. So I could either make one query for each department, or
pull all 4 at the same time. I was thinking that doing the latter when
the report opens and basing all the graphs off that data would be the
best, but I don't know how to do that.
The other problem is that the reports have to break our data down on
either a weekly or monthly basis. There are thousands of records per
year which the query right now groups using DateDiff. I'm also
thinking about adding another table or column which will permanently
store the week number instead of having to compute it in a query. The
performance isn't bad when the database is local on my desktop, but
over the shared network it becomes a problem.
Thanks