Roz Clarke
roz.clarke at donnslaw.co.uk
Thu Jun 12 08:18:57 CDT 2003
Hi Tina To be honest I'm not sure exactly why nested queries are so slow but I think your suspicion is close to the truth. However you can run a series of queries in code using DoCmd.RunQuery, then someone just has to kick the code off and all the queries will run in turn. Roz -----Original Message----- From: Tina Norris Fields [mailto:tinanfields at torchlake.com] Sent: 12 June 2003 14:06 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