Gustav Brock
Gustav at cactus.dk
Tue Sep 18 04:17:53 CDT 2007
Hi Mark Oh, but the recordset, was that retrieved from SQL Server or a (local) Access database? Did you try to open it static and/or as a snapshot? /gustav >>> markamatte at hotmail.com 18-09-2007 04:24 >>> Hello All, I tried the suggestion below...using 10k filters instead of 10K SQL statements...it actually took 3 times as long. I need the fastest approach to executing 10K SQL Statements/Sets of Criteria. The 10K are all againts the same 3K row table. Any ideas?> Thanks, Mark A. Matte >From: "Gustav Brock" <Gustav at cactus.dk> >Reply-To: Access Developers discussion and problem >solving<accessd at databaseadvisors.com> >To: <accessd at databaseadvisors.com> >Subject: Re: [AccessD] SQL against recordset >Date: Tue, 04 Sep 2007 16:30:10 +0200 > >Hi Mark > >To initiate an SQL Execute is slow. Running DAO on a recordset is very >fast, indeed when you have only 3K records. >So open a recordset and apply the 10K filters - my guess is a 10 fold speed >increase or more. > >/gustav > > >>> markamatte at hotmail.com 04-09-2007 16:12 >>> >This is the speed thing again. I am running 10K SQL statements against a 3K >row table. I need it to be as fast as possible. Currently my 10K >statements are stored in a table. I pull them in as a recordset...loop >through...and execute each one. The 10K are all looking at the same >table...just different sets of criteria. A friend suggested I pull the data >into a recordset...and have each SQL statement reference the recorset...as >an attempt to save time. Maybe an array? > >Any thoughts? > >Thanks, > >Mark A. Matte