extremely slow performance

[Denise]

I converted my Access 2000 FE and BE to Access 2007 FE and BE. At the same
time the administrator moved everything to 2008 server. Since them when i
have been experiencing extreme slowdown. Today my users reported it taking 10
minutes just to open the first screen and log on which sets the persistant
LDB and logs user on. At the same time i got directly on the server and ran
my FE from the desktop to the BE one directory down from the root. I
experienced no slow down. Besides having a persistant ldb i have also set
subdatasheet to none. i have never experienced these slow problems with my
program until the change from 2000. Suggestions please. What bothers me is
this is extreme.

 

[Alex Dybenko]

Hi,
try to run 2000 version on new server or 2007 on old - this will help you to
locate the source of problem.
Look at:
http://www.granite.ab.ca/access/performancefaq.htm

--
Best regards,
___________
Alex Dybenko (MVP)
http://accessblog.net
http://www.PointLtd.com

 

[Linq Adams via AccessMonster.com]

Allen Browne has a list of all Hotfixes for 2007. Anumber of these apply to
speeding up various operations. Go to here

http://allenbrowne.com/Access2007.html

and put "Slow" into the Find box to find the one that applies to your
particular problem.

 

[David W. Fenton]

I converted my Access 2000 FE and BE to Access 2007 FE and BE. At
the same time the administrator moved everything to 2008 server.
Since them when i have been experiencing extreme slowdown. Today
my users reported it taking 10 minutes just to open the first
screen and log on which sets the persistant LDB and logs user on.
At the same time i got directly on the server and ran my FE from
the desktop to the BE one directory down from the root. I
experienced no slow down. Besides having a persistant ldb i have
also set subdatasheet to none. i have never experienced these slow
problems with my program until the change from 2000. Suggestions
please. What bothers me is this is extreme.

The easiest thing to try is to delete all the table links in your
front end and recreate them for the new server. Since A2000, there
has been an issue with metadata stored in the linked tables
sometimes causing major problems when you just update the CONNECT
string for them instead of recreating them from scratch (which
corrects the problem as there's no legacy metadata).