Multi User Database - Speed

  • Thread starter Thread starter Frank
  • Start date Start date
F

Frank

Ok...I think I've spent the last two days thumbing through
these posts looking for suggestions/tips/tricks on how to
speed up a multi-user database.

I cannot split the database to a server because in the
three attempts at doing so, I cannot even access it using
the front-end, my pc just freezes up. So, users access
this database from the server itself.

My biggest problem I am running into is, when more than
one user have the database open, the speed dramtically
decreases and querying is much slower. Any help would be
most appreciated.

(I have consolidated many times, which helps, but it's not
a long term solution. I have also made sure each user has
the latest Jet Service Pack).
Thanks
 
Thanks for the website reference. I can split the
database just fine, but as soon as I do that, everything
slows down to a standstill. If I leave the entire
application on the server and access it w/out splitting,
it runs fine until more than one person runs it. I'm
still trying to grasp the LDB tip on the website, that
looks like it may work, but not sure until I try.

What if I had a lot of controls on a single form, or a lot
of fields on one query? Would that slow things down
dramatically?
-----Original Message-----
If you can't split the database and make it usable, you have other issues
going on. That is usually no-brainer.

In any case, see
http://www.granite.ab.ca/access/performancefaq.htm for
 
How fast is your network? 100Mbps? 10Mbps? Wireless? WAN? If you are
running anything less than 100Mbps on a wired network, performance may be
sluggish. Wireless and WAN are not recommended, and could lead to
corruption.

The LDB tip provides a HUGE improvement...especially when relinking tables.

Yes, a large number of controls or subforms can make a database appear slow
too. With subforms, I usually put them on a tab control and only bind the
subform when the tab is made visible....this trick can make a big difference
too. Try to minimize the number of records your return in queries by
including criteria. Also, minimize the number of columns/fields to the
number that are really needed.
 
frank said:
Thanks for the website reference. I can split the
database just fine, but as soon as I do that, everything
slows down to a standstill. If I leave the entire
application on the server and access it w/out splitting,
it runs fine until more than one person runs it. I'm
still trying to grasp the LDB tip on the website, that
looks like it may work, but not sure until I try.

From your description of your environment and problem the LDB tip is
likely the biggest problem.
What if I had a lot of controls on a single form, or a lot
of fields on one query? Would that slow things down
dramatically?

Yes but not dramatically.

Tony
--
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
 
Back
Top