[AccessD] Make-Table Queries Combined

Tina,

  Yes, Access is trying to run the whole thing as one transaction.  A better
approach is code (or a macro) to run each of the  32 queries on it's one.
Then it becomes a single button operation.

Jim Dettman
President,
Online Computer Services of WNY, Inc.
(315) 699-3443
jimdettman at earthlink.net

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Tina Norris
Fields
Sent: Thursday, June 12, 2003 9:06 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] Make-Table Queries Combined


Hi List,

A friend's company has this situation:

A particular report is actually based on about 32 make-table queries.
 Running them one at a time works well, but requires someone to run each
one in sequence.  My friend combined these small queries into a big one
that gathers them all together.  He finds that when it gets to about the
14th query, everything slows down to a crawl.  In fact, it may take up
to 12 hours for the large combining query to finish its job.  I don't
know anything more about this situation.

Does anyone here know why this happens?  Is it something like the system
has to keep everything in memory until the query finishes?

Thanks for your thoughts.

Tina

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com