By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,841 Members | 1,675 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,841 IT Pros & Developers. It's quick & easy.

Access going slow on new server hardware setup

P: n/a
This is about a mysterious slow down only.
An application (split data & FE) that has run for 6 years without
error with six to ten users. The hardware (not my job) has been
‘updated' and a new fast server added.
The data has been moved to the server and the program exists on each
separate user's pc.
The original program version in Ac97 for data and program was then
updated into Ac2000 as it appeared to use less resources but it is
just the same, if not slower! All systems are Win XP and users all
have 256Kb RAM. The server has 1Gb. (but clearly Jet does not use any
of it)

What should be going 7 times faster is now running 8 to 60 times
slower. It now takes nearly 2mins to load the program off the desktop
icon instead of 2 seconds. Opening the main data screen is now 25 secs
instead of 2 to 3 seconds. Once into the main forms it is fine, no
problem. But as I say loading is just way off the 5sec max.

The first user in will load instantly but every subsequent user has a
long frustrating wait.

Has anyone any idea why? Lets not forget that the only thing to change
is the hardware. The program code & setup has not changed at all. What
should be seriously faster is now unexplainably slower!

Is more memory for users the answer? Any experience to point to the
fix appreciated.
Nov 12 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
en********@ukonline.co.uk (Bill Elgie) wrote:

Sounds to me like a lot of things got upgraded at the same time. Both client
hardware and OS, server hardware and OS and Office.

Was the old client OS Win 9x (95, 98 or ME)? What was the old server OS?
The first user in will load instantly but every subsequent user has a
long frustrating wait.


The three most common performance problems in Access 2000 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
Nov 12 '05 #2

P: n/a
Tony Toews <tt****@telusplanet.net> wrote in message news:<87********************************@4ax.com>. ..
en********@ukonline.co.uk (Bill Elgie) wrote:

Sounds to me like a lot of things got upgraded at the same time. Both client
hardware and OS, server hardware and OS and Office.

Was the old client OS Win 9x (95, 98 or ME)? What was the old server OS?


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~
Thanks for that Tony, I will make the changes indicated & test them
out.

Regards the upgrade, initially only the hardware was upgraded from
PIIs with 56KbR to 128KbR and Windows98 with one pc storing the
backend database. These were replaced with a supadupa server and new
pcs. I changed it to Ac2000 later as it seemed that WinXP used far
less resources with that than with AC97 and I thought/hoped that it
would improve the speed problem. I didn't just recompile into Ac2000,
it was totally rewritten and upgraded to take advantage of improved
functionality and use our current tools/functions.

It will be a week before I can get back to reinstall but will file the
results in case it helps others.

Bill
Nov 12 '05 #3

P: n/a
Rob
I am almost SURE I know what your problem is. Ran into the exact same
thing in my move from slower machines with Accesss 97 on them to
faster machines with Access 2000 on them and the speed of my
application decreased DRAMATICALLY.

Access 2000 installs by default with "Track name autocorrect info" set
to ON.
This "feature" was not available in Access97.
If you are doing anything tricky behind your forms, like changing
querydefs or recordsources on the fly, Access is trying to keep track
of these changes and propagate them....UGH.
Turn this off and your app should increase in speed quite a bit.
Let me know if this helped.
Nov 13 '05 #4

P: n/a
Well I have to say that the changed suggested by Tony Toews worked
just fine. When a new version first runs it re-links the data, about
18 tables. The unlink & relink now is 30secs from around 2mins. When
the program runs it is on the screen so fast that I cannot measure it.
Previously up to a min and a half was the time. It is now a totally
different program and everything is well within the 5sec max for
opening screens that we specify.

Additionally I modified the A97 version and that is as fast if not
faster than the A2k version in the same environment. I have to say
that the unsetting of the Autocorrect didn't seem to make a great
difference. I think that the persistant table is the main thing. In
A2k I did set SubDataSheet name to [None] in every table in the system
including all tables in the front end mde.

I take this opportunity to thank Tony, initially for reading and
replying my question and secondly for his suggestions on a solution, I
really am very grateful for his effort.
(so often in the past when I have posted a similar question, I
received a range of answers from guys that totally ignored my
original. One chap actually chopped up my original question, totally
changing the meaning of it and then replied to the changes!...maybe
it's an attempt at humour? but you can see examples of it time and
time again in google, it can be quite frustrating)

Thanks again for a total conclusion and solution that resulted in a
totally changed application.
Regards Bill
Nov 13 '05 #5

P: n/a
en********@ukonline.co.uk (Bill Elgie) wrote:
Was the old client OS Win 9x (95, 98 or ME)? What was the old server OS?


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~
Thanks for that Tony, I will make the changes indicated & test them
out.

Regards the upgrade, initially only the hardware was upgraded from
PIIs with 56KbR to 128KbR and Windows98 with one pc storing the
backend database. These were replaced with a supadupa server and new
pcs. I changed it to Ac2000 later as it seemed that WinXP used far
less resources with that than with AC97 and I thought/hoped that it
would improve the speed problem. I didn't just recompile into Ac2000,
it was totally rewritten and upgraded to take advantage of improved
functionality and use our current tools/functions.


Ok, the reasons for the performance slowdown all make sense from what I've seen
personally and read in the newsgroups.

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
Nov 13 '05 #6

P: n/a
en********@ukonline.co.uk (Bill Elgie) wrote:
I take this opportunity to thank Tony, initially for reading and
replying my question and secondly for his suggestions on a solution, I
really am very grateful for his effort.


Thanks muchly. Glad to hear we can help out.

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
Nov 13 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.