Access 2007 slow in multi-user environment

[BillE]

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]]

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]

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

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/

 

[Tony Toews [MVP]]

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.

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/

 

[Jim Bunton]

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]]

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
--
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/