Open Query Design View or Saving Extremely SLOW

Access 2007. Often I create a query based on several tables, and have to
split up the work of the queries into subsequent queries so that the
evaluation is not to complex. The problem is, whenever I go back to edit or
save these queries, it takes forever (2 minutes or more) to load or save. I
understand that it is checking the underlying or child queries, but there has
to be a quicker way to access these for edit --- Creating unecessary TABLES
instead of these underlying queries would eliminate the check --- but this is
a total waste of space. Are there any better solutions?

There are too many variables that could be involved to answer this here.

Bonnie
http://www.dataplus-svc.com

dbarmer wrote:
Access 2007. Often I create a query based on several tables, and have to
split up the work of the queries into subsequent queries so that the
evaluation is not to complex. The problem is, whenever I go back to edit or
save these queries, it takes forever (2 minutes or more) to load or save. I
understand that it is checking the underlying or child queries, but there has
to be a quicker way to access these for edit --- Creating unecessary TABLES
instead of these underlying queries would eliminate the check --- but this is
a total waste of space. Are there any better solutions?

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...eries/200912/1

Show us an example of the SQL of a query that is too complex. Maybe we could
see a way to shorten it up some, like using an alias, or see a problem with
the structure of your tables.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"dbarmer" wrote:

Access 2007. Often I create a query based on several tables, and have to
split up the work of the queries into subsequent queries so that the
evaluation is not to complex. The problem is, whenever I go back to edit or
save these queries, it takes forever (2 minutes or more) to load or save. I
understand that it is checking the underlying or child queries, but there has
to be a quicker way to access these for edit --- Creating unecessary TABLES
instead of these underlying queries would eliminate the check --- but this is
a total waste of space. Are there any better solutions?