[AccessD] I wrote a program, about a year ago, and it contain s two unbound reports. Each of these reports has

A couple of things.  First, make sure you are indexing the age field.  (That
way, it just has to count the indexes that are over sixty....it's
faster....).  Next, make sure the database is compacted (which re-indexes
everything).

Finally, are you constantly using DCount over and over, or are you just
doing it twice?  If you are running it over and over, I would just pull the
value you want, and store it in a variable, OR, if you are pulling up a
'list' of values, pull it as a recordset, with a query, and run through the
recordset.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of John Clark
Sent: Thursday, March 25, 2004 3:41 PM
To: accessd at databaseadvisors.com
Subject: [AccessD] I wrote a program, about a year ago, and it contains
two unbound reports. Each of these reports has


I wrote a program, about a year ago, and it contains two unbound
reports. Each of these reports has 83 calculated (i.e. statistical)
fields on them--they are actually pretty identical with exception that
one is a quarterly and the other is a cumulative calculation. 
 
The calculations are mostly similar, for example: 
 
    =DCount("[xAge]","qryOver60-Cumulative","[XAge] >= 60")
 
    =DCount("[xAge]","qryOver60-SC-Cumulative","[XAge] >= 60 And
[fndCSE] = True And [logLowInc] = True")
 
    =DCount("[Legal]","qryPartIII-SC","[Legal] = True")
 
The database (the main table anyhow) has just shy of 7000 records in
it. And it seems like all of the sudden, it is taking quite a bit longer
for the reports to come up and longer to print once they do. I went in
to look at something else today and noticed this. I asked them, if it
seemed slower--I thought maybe it was me--and they agreed.
 
Did I do something wrong in setting this up? Should I have made 83
queries instead? Is it the DCount function (I remember hearing something
on aggregate functions be slow once--maybe)?
 
This is an A2K program--my first one (I only have about 10 or so A97s
out there).
 
There not complaining yet, but I might be, if I were them, so I would
like to head it off, if I can. The state came in their office and they,
"were very impressed with [the] program," which is another reason I'd
like to keep on it--maybe they'd be interested further.
 
Thanks for any advise you can give me!
 
Gotta go to a meeting--see y'all!
 
John W Clark
 
-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com