Jim,
I typically use only select queries for reports and forms. There have been rare times when I had a ton of complex calculations that required temporary tables for performance issues.
Without seeing your data and requirements it's difficult to make specific recommendations.
Regards,
Duane
Sent: Monday, February 19, 2018 10:10 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Daisy Chain queries question
Hello all,
I was reading an article this weekend about daisy chaining queries together. And after inheriting a lot of databases since the retirement of my boss, I have been faced with some things that I feel could be more efficient. So this article peaked my interest.
So the situation is that I have found a macro that runs many queries to create several tables and to ultimately run a report at the conclusion of the macro. There are several strings of queries that have make table queries and append and update queries following the make table query. The building of the next table is built from the previous make table query and this goes on for several instances of queries. For example
qry1 makes table tbl1
qry2 uses tbl1 which makes table tbl2
qry3 uses tbl2 makes table tbl3
qry4 uses tbl3 makes table tbl4
qry5 uses tbl4 makes table tbl5
So I saw the daisy chain solution and thought of the efficiency of the daisy chain. So my question is would it be beneficial and more efficient to change the make table queries to select queries and use them in the next query for the source.
for example
qry1 is the source of qry2
qry2 is the source of qry3
qry3 is the source of qry4
and so on.
Thank You
Jim Wagner
Posted by: Duane Hookom <duanehookom@hotmail.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (2) |
Tidak ada komentar:
Posting Komentar