Access 2007 slow in multi-user environment

BillE

unread,

Dec 14, 2007, 3:38:42 PM12/14/07

to

I have split the Access 2007 application into FE and BE.
FE is on user's desktops (not a shortcut), BE is on the network. Users are
using XP, not Vista.
Opening the first FE is very fast.
Opening the FE on a second machine takes several seconds, displaying a blank
screen.
Opening the FE on a third machine takes minutes, displaying a blank screen.

I'm not sure why the performance is so poor. I would appreciate any
guidance.
Thanks
Bill

Tony Toews [MVP]

unread,

Dec 14, 2007, 7:32:58 PM12/14/07

to

"BillE" <bel...@datamti.com> wrote:

>I have split the Access 2007 application into FE and BE.
>FE is on user's desktops (not a shortcut), BE is on the network. Users are
>using XP, not Vista.
>Opening the first FE is very fast.
>Opening the FE on a second machine takes several seconds, displaying a blank
>screen.
>Opening the FE on a third machine takes minutes, displaying a blank screen.

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

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

bill

unread,

Dec 19, 2007, 11:11:01 AM12/19/07

to

Thanks! I implemented all your suggestions (except the decompile, which I
kept in reserve) and something did the trick. I didn't have the opportunity
to test them individually to figure out what did it, but now it hums along
nicely.

--
bill

Tony Toews [MVP]

unread,

Dec 20, 2007, 7:04:17 PM12/20/07

to

bill <bel...@hotmail.com> wrote:

>Thanks! I implemented all your suggestions (except the decompile, which I
>kept in reserve) and something did the trick. I didn't have the opportunity
>to test them individually to figure out what did it, but now it hums along
>nicely.

Glad to hear it's working. The reality is you pretty much need to
do most of those things to get good performance. So no sense in just
trying to do a few.

Jim Bunton

unread,

Dec 21, 2007, 5:01:39 PM12/21/07

to

I would appreciate it if the list of suggestions for dealing with slowness
in a multiuser environment could be posted again - can't find it through
this posting

Jim Bunton

"Tony Toews [MVP]" <tto...@telusplanet.net> wrote in message
news:mm0mm3h61a226en48...@4ax.com...

Tony Toews [MVP]

unread,

Dec 23, 2007, 6:31:22 PM12/23/07

to

"Jim Bunton" <wbbr...@blueyonder.co.uk> wrote:

>I would appreciate it if the list of suggestions for dealing with slowness
>in a multiuser environment could be posted again - can't find it through
>this posting

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

If the problem is for everyone when starting up the MDB then it likely
needs a decompile.

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

Tony