Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / March 2008

Tip: Looking for answers? Try searching our database.

DSUMs Causing Slow Response from Split Database

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Tom - 11 Mar 2008 23:59 GMT
All,

I recently split my first database application into a front end/back
end server application for distributed users to get out of managing
the day to day data entry and to focus on more productive activities.
All appears to be working as intended with one very major exception.
It appears that any queries (or reports relying on queries) containing
DSUMs are running painfully slow.  I'm fairly certain the DSUMs are
the culprit given before and after performance comparisons.  I realize
now it was a bad decision to use DSUMs, even for a novice hack like
myself.

What's the best path forward to replace all the DSUMs with something
faster in a multi-user, server-based environment?

Note:  I generally have no more than five users connected
simultaneously, and all traffic is confined to a corporate intranet
for the time being.

Thanks for your advice,

Tom
Armen Stein - 12 Mar 2008 17:03 GMT
>All,
>
[quoted text clipped - 18 lines]
>
>Tom

Often a DSUM can be replaced by creating another Totals query that
calculates the value that needs to be summed, then joining it to your
main query.

The totals query will calculate the Sum values all at once, which is
usually much more efficient than DSUMs.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com
Tony Toews [MVP] - 15 Mar 2008 04:29 GMT
>I recently split my first database application into a front end/back
>end server application for distributed users to get out of managing
>the day to day data entry and to focus on more productive activities.

There may be other things that can also help with performance in a
multi user environment.   Mind you removing DSUMs would be very high
on my list too.

The three most common performance problems in Access 2000 or newer
are:
 - LDB locking which a persistent recordset connection or an always
open bound form corrects (multiple users)
 - sub datasheet Name property set to [Auto] should be [None]
 - Track name AutoCorrect should be off

For more information on these, less likely causes, other tips and
links to MS KB articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

I specifically created the Auto FE Updater utility so that I could
make changes to the FE MDE as often as I wanted and be quite confident
that the next time someone went to run the app that it would pull in
the latest version.  For more info on the errors or the Auto FE
Updater utility see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the
FE on each PC up to date.

Tony

Signature

Tony Toews, Microsoft Access MVP
  Please respond only in the newsgroups so that others can
read the entire thread of messages.
  Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
  Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

david@epsomdotcomdotau - 15 Mar 2008 06:21 GMT
A DSUM sums the values across a bunch of records.  If you have
10 records, it is 10 times slower than if you have 1 record.

That has nothing to do with if DSUM is slow: it is just the design
of your query.

So the first thing is always to think about how many records you
are summing, and how often you are doing it.

Sometimes it is even better to make a temporary table and put all
your sums in that, so that you don't have to do it again and again.

Sums in the criteria section are particularly bad: sums that have
record-based criteria are even worse (much worse). That is,
sums like DSUM("field","table","fld_2 =" + [fld_3)

Sometimes it is worthwhile to replace all the DSUM with your own
DSUM function, like this: http://mvps.org/access/modules/mdl0012.htm
(This makes less difference now than it did when it was written)

> All,
>
[quoted text clipped - 18 lines]
>
> Tom
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.