Access Back End Sometimes Freezes

[JvC]

Background:
I have a customer running a front end/back end Access 2007 database.
Normally, there are 3 users, and occasionally there are 4. Back end
database is located on a straight PC running Windows XP Professional.
It no keyboard/monitor, and is only used by 1 remote user, using
LogMeIn. That PC has an Intel Dual Core processor, 4 GB RAM and a 160
GB SATA drive that is about 1/2 full. The clients computers vary in
age, but all have at least 2 GB of RAM and are running XP Professional.

The largest table in the back end is approximately 3,500 rows. I have
reviewed all of the tables and indexes, and they appear to be
appropriate (I inherited the original system!)

Problem:
Occasionally, when opening a bound form, the system freezes, sometimes
for up to a minute. It happens on all of the clients, including remote
via LogMeIn, so I believe I have a server problem.

Questions:
1) Has anyone else experienced this and know a viable solution?
2) Would upgrading the server to Windows Server 2003 have any affect,
positive or negative? The hardware consultant says it would decrease
performance, but I do not trust his judgement on software (he upgraded
everyone to Office 2007 from 2003 "because they needed it." They
didn't..

Any suggestions would be appreciated!

Thanks!

John

[Albert D. Kallal]

I would walk thought tony's performance faq here:

http://www.granite.ab.ca/access/performancefaq.htm

One trick I would try is keeping a persistence connection open. I don't
suppose any cd rom/dvd backup is occurring on this machine? Perhaps a
network printer attached?

Questions:
1) Has anyone else experienced this and know a viable solution?

The persistent connection trick comes up a lot as a solution. Another
slowdown for me occurred on a machine that had a file in the spooler but the
printer was not able to print...it seemed windows was trying too hard to
print and it made the computer sluggish.

2) Would upgrading the server to Windows Server 2003 have any affect,
positive or negative? The hardware consultant says it would decrease
performance, but I do not trust his judgement on software (he upgraded
everyone to Office 2007 from 2003 "because they needed it." They didn't..

The above is a shot in the dark. As for a reducit, he might be right since
the server edtions of wdinwos manages file rights and secirty..and of a LOT
more traffic can result.

A few other things would be to:

Always deploy a mde (accde) for the front ends (they can't be modified or be
un-compiled like a accDB can.

You could also ensure that virus software is ignoring, or not scanning the
files..as often that can be an issue.

Best bets:
check tony's faq, and try a persistent connection....
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com

[JvC]

Thanks, Albert!

Albert D. Kallal brought next idea :

I would walk thought tony's performance faq here:

http://www.granite.ab.ca/access/performancefaq.htm

One trick I would try is keeping a persistence connection open. I don't
suppose any cd rom/dvd backup is occurring on this machine? Perhaps a network
printer attached?

>Questions:
1) Has anyone else experienced this and know a viable solution?

The persistent connection trick comes up a lot as a solution. Another
slowdown for me occurred on a machine that had a file in the spooler but the
printer was not able to print...it seemed windows was trying too hard to
print and it made the computer sluggish.

>2) Would upgrading the server to Windows Server 2003 have any affect,
positive or negative? The hardware consultant says it would decrease
performance, but I do not trust his judgement on software (he upgraded
everyone to Office 2007 from 2003 "because they needed it." They didn't..

The above is a shot in the dark. As for a reducit, he might be right since
the server edtions of wdinwos manages file rights and secirty..and of a LOT
more traffic can result.

A few other things would be to:

Always deploy a mde (accde) for the front ends (they can't be modified or be
un-compiled like a accDB can.

You could also ensure that virus software is ignoring, or not scanning the
files..as often that can be an issue.

Best bets:
check tony's faq, and try a persistent connection....

[Tony Toews [MVP]]

JvC <jo******@earthlink.netwrote:

>2) Would upgrading the server to Windows Server 2003 have any affect,
positive or negative? The hardware consultant says it would decrease
performance, but I do not trust his judgement on software (he upgraded
everyone to Office 2007 from 2003 "because they needed it." They
didn't..

I rather doubt upgrading to Win Server 2003 would make a significant difference in
performance. A client in 1999 was running a 150 Mhz NT 4.0 server and we were
getting good performance on a A97 database with 100K records in some tables.

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

JvC <jo******@earthlink.netwrote:

>Occasionally, when opening a bound form, the system freezes, sometimes
for up to a minute. It happens on all of the clients, including remote
via LogMeIn, so I believe I have a server problem.

Try the persistent connection as Albert suggests. If that doesn't solve the problem
post back.

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/