How to Energize a Dreadfully Slow Query

There must be a way to enhance the performance of a query, or find a
plausible workaround, but I seem to be hitting a wall. I have tried a
few tweaks, however, there has been no improvement.

Simply, I'm including one calcualtion from a separate table/query. It
sums the total units sold to date by ProductID number and is used in
other select queries to perform various calculations. Perhaps there is
an advantage in working with a maximum number of records that would be
used in the database in order to fully evaluate real-world conditions.
In this case, there are nearly 10,000 records.

I have tried DSum and a Function SumUnits(ProductID), but the
performance of either is nearly the same. It takes about 25 seconds
after clicking sort or filter on any of the calculated columns on the
form before it is completed - yuk. Tried a Totals query to check the
speed and voila, just a couple of seconds, but of course, it doesn't
matter how or where a Totals query is used as it renders any other
select query non-updatable.

Have thought about using an Update query to store a 'calculated value'
as an alternative, but that method is generally boohooed. But even
going that route, it would still take at least 25 seconds everytime the
form is opened to refresh the numbers, but of course, once opened any
resorting or refiltering would be instant.

All of the other calculations on the query are very basic, no DSum's,
no DLookup's, etc. And by temporarily removing the UnitsSold to date
field above, performance is under a second. Any suggestions will be
welcomed.

Thanks, Rolan

re: How to Energize a Dreadfully Slow Query

You could open a recordset from code that is the group by w/ sum, and create a
function that uses FindFirst to get the correct sum from the open recordset.

On 28 Jan 2005 07:03:37 -0800, "Rolan" <continue@safe-mail.net> wrote:
[color=blue]
>There must be a way to enhance the performance of a query, or find a
>plausible workaround, but I seem to be hitting a wall. I have tried a
>few tweaks, however, there has been no improvement.
>
>Simply, I'm including one calcualtion from a separate table/query. It
>sums the total units sold to date by ProductID number and is used in
>other select queries to perform various calculations. Perhaps there is
>an advantage in working with a maximum number of records that would be
>used in the database in order to fully evaluate real-world conditions.
>In this case, there are nearly 10,000 records.
>
>I have tried DSum and a Function SumUnits(ProductID), but the
>performance of either is nearly the same. It takes about 25 seconds
>after clicking sort or filter on any of the calculated columns on the
>form before it is completed - yuk. Tried a Totals query to check the
>speed and voila, just a couple of seconds, but of course, it doesn't
>matter how or where a Totals query is used as it renders any other
>select query non-updatable.
>
>Have thought about using an Update query to store a 'calculated value'
>as an alternative, but that method is generally boohooed. But even
>going that route, it would still take at least 25 seconds everytime the
>form is opened to refresh the numbers, but of course, once opened any
>resorting or refiltering would be instant.
>
>All of the other calculations on the query are very basic, no DSum's,
>no DLookup's, etc. And by temporarily removing the UnitsSold to date
>field above, performance is under a second. Any suggestions will be
>welcomed.
>
>Thanks, Rolan[/color]

re: How to Energize a Dreadfully Slow Query

On 28 Jan 2005 07:03:37 -0800, "Rolan" <continue@safe-mail.net> wrote:

Hi
Not sure I unerstand this but if the totals query is so fast, can't
you make a temporary table from it and use this to make the main
query/queries updateable?
David

re: How to Energize a Dreadfully Slow Query

Well, let's think about your form design. If you have a continuous style
form where one of the controls is a Domain function (DSum, DCount, etc.),
then a query to calculate that value is run once for each record. As you've
discovered, this can take some time, when loading many records. Besides the
(perhaps not so) obvious help that indexing on any/most fields you search or
sort, I think you might consider removing the calculated value from the
continuous detail section, and moving it to a pop-up form that users could
view on demand. Put a command button in the main form's header/footer that
would open that form, with a criteria link to the current detail record.
-Ed

"Rolan" <continue@safe-mail.net> wrote in message
news:1106924617.331838.239220@c13g2000cwb.googlegr oups.com...[color=blue]
> There must be a way to enhance the performance of a query, or find a
> plausible workaround, but I seem to be hitting a wall. I have tried a
> few tweaks, however, there has been no improvement.
>
> Simply, I'm including one calcualtion from a separate table/query. It
> sums the total units sold to date by ProductID number and is used in
> other select queries to perform various calculations. Perhaps there is
> an advantage in working with a maximum number of records that would be
> used in the database in order to fully evaluate real-world conditions.
> In this case, there are nearly 10,000 records.
>
> I have tried DSum and a Function SumUnits(ProductID), but the
> performance of either is nearly the same. It takes about 25 seconds
> after clicking sort or filter on any of the calculated columns on the
> form before it is completed - yuk. Tried a Totals query to check the
> speed and voila, just a couple of seconds, but of course, it doesn't
> matter how or where a Totals query is used as it renders any other
> select query non-updatable.
>
> Have thought about using an Update query to store a 'calculated value'
> as an alternative, but that method is generally boohooed. But even
> going that route, it would still take at least 25 seconds everytime the
> form is opened to refresh the numbers, but of course, once opened any
> resorting or refiltering would be instant.
>
> All of the other calculations on the query are very basic, no DSum's,
> no DLookup's, etc. And by temporarily removing the UnitsSold to date
> field above, performance is under a second. Any suggestions will be
> welcomed.
>
> Thanks, Rolan
>[/color]

re: How to Energize a Dreadfully Slow Query

On 28 Jan 2005 10:08:04 -0600, d.schofieldREMOVE@blueyonder.co.uk (David
Schofield) wrote:
[color=blue]
>On 28 Jan 2005 07:03:37 -0800, "Rolan" <continue@safe-mail.net> wrote:
>
>Hi
>Not sure I unerstand this but if the totals query is so fast, can't
>you make a temporary table from it and use this to make the main
>query/queries updateable?
>David[/color]

People like me keep advocating against Temp tables <g>.

There's a variant on Temp tables that is less problematic. Create a permanent
table in the back-end database that is cache of the group/sum that gets
updated whenever the primary data is changed. This does require a periodic
maintenance process to check and correct the integrity of the sum, though.

re: How to Energize a Dreadfully Slow Query

Thanks everyone for your input. I'm thinking that a variation of the
theme might be a consideration. Since keeping the process reasonably
transparent and seamless is important, perhaps having an Update query
to run on close of the invoice form to post the current UnitsSold
numbers to a new field in the products table might be an acceptable
workaround. Well, the saltmine awaits my return . . .


Steve Jorgensen wrote:[color=blue]
> On 28 Jan 2005 10:08:04 -0600, d.schofieldREMOVE@blueyonder.co.uk[/color]
(David[color=blue]
> Schofield) wrote:
>[color=green]
> >On 28 Jan 2005 07:03:37 -0800, "Rolan" <continue@safe-mail.net>[/color][/color]
wrote:[color=blue][color=green]
> >
> >Hi
> >Not sure I unerstand this but if the totals query is so fast, can't
> >you make a temporary table from it and use this to make the main
> >query/queries updateable?
> >David[/color]
>
> People like me keep advocating against Temp tables <g>.
>
> There's a variant on Temp tables that is less problematic. Create a[/color]
permanent[color=blue]
> table in the back-end database that is cache of the group/sum that[/color]
gets[color=blue]
> updated whenever the primary data is changed. This does require a[/color]
periodic[color=blue]
> maintenance process to check and correct the integrity of the sum,[/color]
though.

re: How to Energize a Dreadfully Slow Query

On Fri, 28 Jan 2005 08:21:40 -0800, Steve Jorgensen
<nospam@nospam.nospam> wrote:
[color=blue]
>On 28 Jan 2005 10:08:04 -0600, d.schofieldREMOVE@blueyonder.co.uk (David
>Schofield) wrote:
>[color=green]
>>On 28 Jan 2005 07:03:37 -0800, "Rolan" <continue@safe-mail.net> wrote:
>>
>>Hi
>>Not sure I unerstand this but if the totals query is so fast, can't
>>you make a temporary table from it and use this to make the main
>>query/queries updateable?
>>David[/color]
>
>People like me keep advocating against Temp tables <g>.
>
>There's a variant on Temp tables that is less problematic. Create a permanent
>table in the back-end database that is cache of the group/sum that gets
>updated whenever the primary data is changed. This does require a periodic
>maintenance process to check and correct the integrity of the sum, though.[/color]
Hi
I know what you mean about avoiding temporary tables.
Aggregation in real time can be a problem, and presummarisation is
unavoidable for large systems, eg OLAP for multi-dimensional data.
However Rolan's problem isn't that the aggregation takes too much time
but that the result of it isn't usable in the context of his query.
How would this be done in other databases?
David

re: How to Energize a Dreadfully Slow Query

"Rolan" <continue@safe-mail.net> wrote in
news:1106930617.759301.19060@c13g2000cwb.googlegro ups.com:
[color=blue]
> Thanks everyone for your input. I'm thinking that a variation of
> the theme might be a consideration. Since keeping the process
> reasonably transparent and seamless is important, perhaps having
> an Update query to run on close of the invoice form to post the
> current UnitsSold numbers to a new field in the products table
> might be an acceptable workaround.[/color]

Don't do it. It will eventually fail.

On a billing app that I created early in my Access career, I did
this to maintain open balances on invoices because the machines the
client was running were substantially slower than my own (I was
running a P120, but they were running P100s that were half as fast
as mine; they were off-brand machines and laptops with very slow
hard drives).

The calculated data was never accurate. It never stayed accurate. It
always got out of line, and it was hard to tell *when* it was wrong,
so you could never depend on the results.

Now, if you are using something other than an MDB to store your data
and have triggers available, that's a different story.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

re: How to Energize a Dreadfully Slow Query

Steve Jorgensen <nospam@nospam.nospam> wrote in
news:1dpkv05hnh6nvthisag7kpq4t8ebjb4iil@4ax.com:
[color=blue]
> People like me keep advocating against Temp tables <g>.[/color]

I think it's a mistake. I learned long ago that sometimes a temp
table is faster than doing the same process in memory, precisely
because derived data can then be indexed, which can vastly speed up
certain kinds of data retrieval processes.

Yes, it seems counter-intuitive, but it turns out that temp tables
don't slow things down at all in those kinds of circumstances.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

re: How to Energize a Dreadfully Slow Query

Rolan wrote:[color=blue]
> There must be a way to enhance the performance of a query, or find a
> plausible workaround, but I seem to be hitting a wall. I have tried a
> few tweaks, however, there has been no improvement.
>
> Simply, I'm including one calcualtion from a separate table/query. It
> sums the total units sold to date by ProductID number and is used in
> other select queries to perform various calculations. Perhaps there is
> an advantage in working with a maximum number of records that would be
> used in the database in order to fully evaluate real-world conditions.
> In this case, there are nearly 10,000 records.
>
> I have tried DSum and a Function SumUnits(ProductID), but the
> performance of either is nearly the same. It takes about 25 seconds
> after clicking sort or filter on any of the calculated columns on the
> form before it is completed - yuk. Tried a Totals query to check the
> speed and voila, just a couple of seconds, but of course, it doesn't
> matter how or where a Totals query is used as it renders any other
> select query non-updatable.
>
> Have thought about using an Update query to store a 'calculated value'
> as an alternative, but that method is generally boohooed. But even
> going that route, it would still take at least 25 seconds everytime the
> form is opened to refresh the numbers, but of course, once opened any
> resorting or refiltering would be instant.
>
> All of the other calculations on the query are very basic, no DSum's,
> no DLookup's, etc. And by temporarily removing the UnitsSold to date
> field above, performance is under a second. Any suggestions will be
> welcomed.
>
> Thanks, Rolan
>[/color]

Do you have a separate totals query? One that gets the total number of
units to date and groups on the product id and may also filter within a
date range? I should think that if you link your query to this totals
query it would zip along quickly.

Are you filtering on a field that isn't indexed?

10,000 records is not a large amount.

Also, is there a need to perform a calculation in the query? If you can
pull the data together first and then present the calculation in the
form or report that would be the optimum method.

re: How to Energize a Dreadfully Slow Query

On Sat, 29 Jan 2005 18:47:19 GMT, Salad <oil@vinegar.com> wrote:
[color=blue]
>Rolan wrote:[/color]
....[color=blue]
>
>Do you have a separate totals query? One that gets the total number of
>units to date and groups on the product id and may also filter within a
>date range? I should think that if you link your query to this totals
>query it would zip along quickly.[/color]

It sounds as if he tried that first, but he needed it to be editable, and that
query isn't.

re: How to Energize a Dreadfully Slow Query

Please excuse the lack of punctuality and thanks for all of the
suggestions from everyone. I implemented the following and so far it
seems to work very well, not to mention that it is extremely fast by
comparsion. I presume this is a derivative of a temporary table
process. Perhaps on a small network of 3 or 4 users most potential
problems should be mitigated.

I took the Totals query (PartID, PartNumber and SoldQty) and converted
it to a Make-Table query, then added code to the OnClose event of the
Invoice form to update (replace) the table with the most current,
accumulative sold parts data. Then in the four or five other queries
that include the sold to date column, I linked the Make-Table PartID
number to the same of tblParts. The calculations of other columns using
the sold data work fine, but the performance boost in resorting and
filtering is in a word "astonishing", plus they all remain updatable
queries. Even a small time lag of a few minutes before an invoice is
closed is tenable and should cause no adverse effects.

Thanks again,

Rolan


Steve Jorgensen wrote:[color=blue]
> On Sat, 29 Jan 2005 18:47:19 GMT, Salad <oil@vinegar.com> wrote:
>[color=green]
> >Rolan wrote:[/color]
> ...[color=green]
> >
> >Do you have a separate totals query? One that gets the total number[/color][/color]
of[color=blue][color=green]
> >units to date and groups on the product id and may also filter[/color][/color]
within a[color=blue][color=green]
> >date range? I should think that if you link your query to this[/color][/color]
totals[color=blue][color=green]
> >query it would zip along quickly.[/color]
>
> It sounds as if he tried that first, but he needed it to be editable,[/color]
and that[color=blue]
> query isn't.[/color]

re: How to Energize a Dreadfully Slow Query

If you're using a Make Table query, it's not a derivative of the temporary
table solution, it -is- the temporary table solution. That's OK, but be aware
of the pitfalls.

Your front-end will now bloat, and need to be compacted, plus the extra
activity means that it's more likely the front-end may become corrupted at
some point. Finally, in spite of your beste efforts, it may not be possilbe
to completely prevent the front-end from being opened in more than on Access
session at once, so 2 people performing the same operation will step on each
other.

On 30 Jan 2005 18:26:00 -0800, "Rolan" <continue@safe-mail.net> wrote:
[color=blue]
>Please excuse the lack of punctuality and thanks for all of the
>suggestions from everyone. I implemented the following and so far it
>seems to work very well, not to mention that it is extremely fast by
>comparsion. I presume this is a derivative of a temporary table
>process. Perhaps on a small network of 3 or 4 users most potential
>problems should be mitigated.
>
>I took the Totals query (PartID, PartNumber and SoldQty) and converted
>it to a Make-Table query, then added code to the OnClose event of the
>Invoice form to update (replace) the table with the most current,
>accumulative sold parts data. Then in the four or five other queries
>that include the sold to date column, I linked the Make-Table PartID
>number to the same of tblParts. The calculations of other columns using
>the sold data work fine, but the performance boost in resorting and
>filtering is in a word "astonishing", plus they all remain updatable
>queries. Even a small time lag of a few minutes before an invoice is
>closed is tenable and should cause no adverse effects.
>
>Thanks again,
>
>Rolan
>
>
>Steve Jorgensen wrote:[color=green]
>> On Sat, 29 Jan 2005 18:47:19 GMT, Salad <oil@vinegar.com> wrote:
>>[color=darkred]
>> >Rolan wrote:[/color]
>> ...[color=darkred]
>> >
>> >Do you have a separate totals query? One that gets the total number[/color][/color]
>of[color=green][color=darkred]
>> >units to date and groups on the product id and may also filter[/color][/color]
>within a[color=green][color=darkred]
>> >date range? I should think that if you link your query to this[/color][/color]
>totals[color=green][color=darkred]
>> >query it would zip along quickly.[/color]
>>
>> It sounds as if he tried that first, but he needed it to be editable,[/color]
>and that[color=green]
>> query isn't.[/color][/color]

re: How to Energize a Dreadfully Slow Query

Thanks Steve for the word of discouragement :-( Although thinking
about matters of eventuality is a prudent consideration. Prior to the
Make-Table, I had used the following Function as created by Trevor
Best, but specifically constructed for the SoldQty totals only. I
believe you had alluded to using the OpenRecordset method as a better
alternative. Is this more or less what you had in mind?

Using this Function or DSum were nearly identical in performance and
time (25 seconds) when resorting or filtering any of the forms'
calculated columns that contained the SoldQty. Why is it that the
Access Totals query is so much faster? Although I understand why a
Totals query is not updatable, why does it also prevent other query
fields from being updated when linked? Thanks again.



Function tSum (pstrField As String, pstrTable As String, pst*rCriteria
As
String) As Double
On Error GoTo tSum_Err
' Function tSum
' Purpose: Replace DSum, which is slow on attached table*s
' Created: 1 Feb 1996 T.Best


Dim dbCurrent As Database
Dim rstLookup As Recordset
Dim dblValue As Double


Set dbCurrent = dbengine(0)(0)
If pstrCriteria = "" Then
Set rstLookup = dbCurrent.OpenRecordset("Select Sum(*[" &
pstrField & "]) From [" & pstrTable & "]", DB_OPEN_SNAPSHOT)
Else
Set rstLookup = dbCurrent.OpenRecordset("Select Sum(*[" &
pstrField & "]) From [" & pstrTable & "] Where " & pstrCrite*ria,
DB_OPEN_SNAPSHOT)
End If
If Not rstLookup.bof Then
rstLookup.MoveFirst
dblValue = rstLookup(0)
Else
dblValue = 0
End If
rstLookup.Close
tSum = dblValue


tSum_Exit:
On Error Resume Next
rstLookup.Close
Exit Function


tSum_Err:
MsgBox Error, 16, "Error " & Err
Resume tSum_Exit
End Function





Steve Jorgensen wrote:[color=blue]
> If you're using a Make Table query, it's not a derivative of the[/color]
temporary[color=blue]
> table solution, it -is- the temporary table solution. That's OK, but[/color]
be aware[color=blue]
> of the pitfalls.
>
> Your front-end will now bloat, and need to be compacted, plus the[/color]
extra[color=blue]
> activity means that it's more likely the front-end may become[/color]
corrupted at[color=blue]
> some point. Finally, in spite of your beste efforts, it may not be[/color]
possilbe[color=blue]
> to completely prevent the front-end from being opened in more than on[/color]
Access[color=blue]
> session at once, so 2 people performing the same operation will step[/color]
on each[color=blue]
> other.
>
> On 30 Jan 2005 18:26:00 -0800, "Rolan" <continue@safe-mail.net>[/color]
wrote:[color=blue]
>[color=green]
> >Please excuse the lack of punctuality and thanks for all of the
> >suggestions from everyone. I implemented the following and so far it
> >seems to work very well, not to mention that it is extremely fast by
> >comparsion. I presume this is a derivative of a temporary table
> >process. Perhaps on a small network of 3 or 4 users most potential
> >problems should be mitigated.
> >
> >I took the Totals query (PartID, PartNumber and SoldQty) and[/color][/color]
converted[color=blue][color=green]
> >it to a Make-Table query, then added code to the OnClose event of[/color][/color]
the[color=blue][color=green]
> >Invoice form to update (replace) the table with the most current,
> >accumulative sold parts data. Then in the four or five other queries
> >that include the sold to date column, I linked the Make-Table PartID
> >number to the same of tblParts. The calculations of other columns[/color][/color]
using[color=blue][color=green]
> >the sold data work fine, but the performance boost in resorting and
> >filtering is in a word "astonishing", plus they all remain updatable
> >queries. Even a small time lag of a few minutes before an invoice is
> >closed is tenable and should cause no adverse effects.
> >
> >Thanks again,
> >
> >Rolan
> >
> >
> >Steve Jorgensen wrote:[color=darkred]
> >> On Sat, 29 Jan 2005 18:47:19 GMT, Salad <oil@vinegar.com> wrote:
> >>
> >> >Rolan wrote:
> >> ...
> >> >
> >> >Do you have a separate totals query? One that gets the total[/color][/color][/color]
number[color=blue][color=green]
> >of[color=darkred]
> >> >units to date and groups on the product id and may also filter[/color]
> >within a[color=darkred]
> >> >date range? I should think that if you link your query to this[/color]
> >totals[color=darkred]
> >> >query it would zip along quickly.
> >>
> >> It sounds as if he tried that first, but he needed it to be[/color][/color][/color]
editable,[color=blue][color=green]
> >and that[color=darkred]
> >> query isn't.[/color][/color][/color]

re: How to Energize a Dreadfully Slow Query

On 30 Jan 2005 19:30:15 -0800, "Rolan" <continue@safe-mail.net> wrote:
[color=blue]
>Thanks Steve for the word of discouragement :-( Although thinking
>about matters of eventuality is a prudent consideration. Prior to the
>Make-Table, I had used the following Function as created by Trevor
>Best, but specifically constructed for the SoldQty totals only. I
>believe you had alluded to using the OpenRecordset method as a better
>alternative. Is this more or less what you had in mind?
>
>Using this Function or DSum were nearly identical in performance and
>time (25 seconds) when resorting or filtering any of the forms'
>calculated columns that contained the SoldQty. Why is it that the
>Access Totals query is so much faster? Although I understand why a
>Totals query is not updatable, why does it also prevent other query
>fields from being updated when linked? Thanks again.[/color]

Ouch - I didn't realize that you wanted to sort or filter on an aggregate
value column. Sorting or filtering on a value that's computed by calling a
procedure is one of the slowest things Access can do. It's not at all what
Jet was optimized for. If that's really a requirement, perhaps, you truly do
need some kind of temporary table solution.

Probably the cleanest-functioning code, though not terribly simple to
implement is to actually create a temporary database, and create the new table
in that database. Actually, although it's a bear to get going for the first
case, you can reuse the code if you have more cases to implement. The steps
are roughly as follows.

1. Check to see if a temporary database has already been created, and
create/open it if not.

1a. Generate a full path to the new database file. When creating the
temporary database, use a Windows API call to get the path to the temporary
directory, but I recommend rolling your own algorithm for the random temporary
file name (it's simpler). Store the new path string in a global variable.

1b. Create the new database and keep a reference to the open database instance
in a global variable.

2. In code, generate SQL for a make table query to populate the new temporary
table in the temporary database. Use the form "SELECT ... INTO <tablename> IN
<databasepath>". Execute this using a temporary Querydef (created with "" for
Name argument).

3. In code, generate the SQL for your form's recordset, joining the local data
to the temporary table. To do this, you'll need to use a "derived table" that
selects from the table in the temp db "[SELECT ... FROM <tempdbtable> IN
<tempdbpath>]. As [<alias>]" in the FROM clause of the main query (as if it
were simply another table).

4. When the app closes, close and delete the temporary database. You can
implement this using a hidden form that is opened either on application
start-up or before the temporary database is first created. When Access
closes, it must close that form, which can perform the clean-up operations via
its Unload event handler.

It's ugly to describe, but it works, it doesn't bloat the front-end or
increase the risk of corruption, and it's insensitive to whether the same
front-end is being shared by multiple Access sessions.

re: How to Energize a Dreadfully Slow Query

And I thought that life was easier before Access . . . Thanks Steve for
your pearls of wisdom. I may have a go at it, but I have the feeling
that it will take me awhile. Instead, how about a pointed message on
the forms, do not sort on marked columns unless you like viewing the
shape of an hourglass :-) Huh?

So apparently you have been there and done that? Are there no other
options that one could implement save bloating the front end? I'm still
wondering and waiting for an answer as to why the Totals query is so
fast when you sum the field, and when used in sorting and filtering.
And why does Access prohibit the updating of fields/controls that are
not a part of a Totals query when one is linked?

Here is an idea. If you have the time, perhaps you can email me a copy
of a sample db that has most of the elements and code that you have
described. That would be a nice gesture. And no rush either - just
whenever :-) My email address as shown is a valid one. Thanks.






Steve Jorgensen wrote:[color=blue]
> On 30 Jan 2005 19:30:15 -0800, "Rolan" <continue@safe-mail.net>[/color]
wrote:[color=blue]
>[color=green]
> >Thanks Steve for the word of discouragement :-( Although thinking
> >about matters of eventuality is a prudent consideration. Prior to[/color][/color]
the[color=blue][color=green]
> >Make-Table, I had used the following Function as created by Trevor
> >Best, but specifically constructed for the SoldQty totals only. I
> >believe you had alluded to using the OpenRecordset method as a[/color][/color]
better[color=blue][color=green]
> >alternative. Is this more or less what you had in mind?
> >
> >Using this Function or DSum were nearly identical in performance and
> >time (25 seconds) when resorting or filtering any of the forms'
> >calculated columns that contained the SoldQty. Why is it that the
> >Access Totals query is so much faster? Although I understand why a
> >Totals query is not updatable, why does it also prevent other query
> >fields from being updated when linked? Thanks again.[/color]
>
> Ouch - I didn't realize that you wanted to sort or filter on an[/color]
aggregate[color=blue]
> value column. Sorting or filtering on a value that's computed by[/color]
calling a[color=blue]
> procedure is one of the slowest things Access can do. It's not at[/color]
all what[color=blue]
> Jet was optimized for. If that's really a requirement, perhaps, you[/color]
truly do[color=blue]
> need some kind of temporary table solution.
>
> Probably the cleanest-functioning code, though not terribly simple to
> implement is to actually create a temporary database, and create the[/color]
new table[color=blue]
> in that database. Actually, although it's a bear to get going for[/color]
the first[color=blue]
> case, you can reuse the code if you have more cases to implement.[/color]
The steps[color=blue]
> are roughly as follows.
>
> 1. Check to see if a temporary database has already been created,[/color]
and[color=blue]
> create/open it if not.
>
> 1a. Generate a full path to the new database file. When creating the
> temporary database, use a Windows API call to get the path to the[/color]
temporary[color=blue]
> directory, but I recommend rolling your own algorithm for the random[/color]
temporary[color=blue]
> file name (it's simpler). Store the new path string in a global[/color]
variable.[color=blue]
>
> 1b. Create the new database and keep a reference to the open database[/color]
instance[color=blue]
> in a global variable.
>
> 2. In code, generate SQL for a make table query to populate the new[/color]
temporary[color=blue]
> table in the temporary database. Use the form "SELECT ... INTO[/color]
<tablename> IN[color=blue]
> <databasepath>". Execute this using a temporary Querydef (created[/color]
with "" for[color=blue]
> Name argument).
>
> 3. In code, generate the SQL for your form's recordset, joining the[/color]
local data[color=blue]
> to the temporary table. To do this, you'll need to use a "derived[/color]
table" that[color=blue]
> selects from the table in the temp db "[SELECT ... FROM <tempdbtable>[/color]
IN[color=blue]
> <tempdbpath>]. As [<alias>]" in the FROM clause of the main query (as[/color]
if it[color=blue]
> were simply another table).
>
> 4. When the app closes, close and delete the temporary database. You[/color]
can[color=blue]
> implement this using a hidden form that is opened either on[/color]
application[color=blue]
> start-up or before the temporary database is first created. When[/color]
Access[color=blue]
> closes, it must close that form, which can perform the clean-up[/color]
operations via[color=blue]
> its Unload event handler.
>
> It's ugly to describe, but it works, it doesn't bloat the front-end[/color]
or[color=blue]
> increase the risk of corruption, and it's insensitive to whether the[/color]
same[color=blue]
> front-end is being shared by multiple Access sessions.[/color]