Access2000 slow in access2002

[Graham]

I have an Access 2000 database with the front end separate
from the data tables (Back end). The front end is on the
clients machine, the back end is on the Win2000 server.
One client uses Win98 and Access 2000 and generates a
report of 380 pages in under 10 seconds (Beautiful!). The
client on Windows XP and Office XP does not get the report
generated until at least 10 minutes has elapsed.

I have tried the knowledge base and changed the tables so
that bus tables is none rather than auto. I changed many
other suggestions in the knowledge base even to the point
of updating SMB protocol files which were suggested as
slowing down ODBC but no luck.

I was wondering if anyone out there had experienced and
resolved this issue.

Thanks in advance

Graham

 

[Sandra Daigle]

Hi Graham,

Have you checked the WinXP/OfficeXP machine for virus scanning software that
might be slowing the process? I have several production systems that are in
use with both Win98/Office2000 and WinXP/OfficeXP and haven't had this type
of issue except when there was virus software on the WinXP machine that was
scanning the mdb.

Also, check this article for other things to consider:

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

 

[Tony Toews]

I have an Access 2000 database with the front end separate
from the data tables (Back end). The front end is on the
clients machine, the back end is on the Win2000 server.
One client uses Win98 and Access 2000 and generates a
report of 380 pages in under 10 seconds (Beautiful!). The
client on Windows XP and Office XP does not get the report
generated until at least 10 minutes has elapsed.

Whenever I see a difference in performance between a Win 95/98/ME
client and a Win NT 4/2000/XP client or after migrating from A97 to
A2000 or newer I immediately suspect that the "recordset open" work
around will help. Second would be the none vs auto which you've
already done.

See the "LDB locking which a persistent recordset connection fixes"
section at the Access Performance FAQ at my website.

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

 

[Wayne]

Hi Graham -

I have seen this issue consistently in a number of
different environments with three of my clients since
Office XP was released. Unfortunately, I have only been
able to resolve the issue by making the recommendation to
my clients and anyone else that may be impacted to not
purchase Office XP until this issue has been acknowledged
and fixed by Microsoft, Inc. This however is not possible
with newer systems that come preloaded with Office XP.

I don't know why this issue is not found in the Knowledge
Base. I have been through many permutations in attempt to
resolve this issue using Office XP. Below are two
significant cases if you are interested in reading about
them. I would really love to have a solid resolution for
this issue.

Case 1: Spalding County Correctional Institution Access
to Access
I developed a Front-End, Back-End (FEBE) solution for
management of Inmates and deployed on a local domain with
15 Gateway desktops (not my call) running Windows 2000 Pro
and one Windows 2000 domain controller. The application
was developed on a machine running Access 2002. After
deploying to the 15 client PCs perfomance fell through the
floor with 5-10 minute response times. The application
and back-end DBs were converted to Access 2002 and
redeployed with no improvement. Finally Access 2000
runtime was installed on the clients and performance was
acceptable.

Case 2: Earthlink, Inc. Access ADP to SQL Server 7
I developed FEBE solution for the reconciliation of
telecoms invoices and deployed on a domain with 20 Dell
desktops and notebooks and 1 SQL Server. The application
was developed as an Access 2000 project (which was a feat
in itself) the back-end was development with SQL Server
7.0. The application performed well when Access 2000 was
installed the the clients. When folks began upgrading to
Office XP performance fell through the floor. Numerous
connections to the server would be opened by any machine
running Office XP and everyone's performance dropped.
Access 2000 Runtime was installed on the clients running
Office XP and the problems went away.

Good blessings,

- Wayne

 

[Jeff]

I have a similar situation, except the variation is between Access 2000 and Access 2002. In fact, the machine with 2002 has a 2.0GB processor and the 2000 machine has a 600MHz and no other hardware conditions that should make the 2002 machine slower than the 2000. The *mdb file is located on the server. Both machines are running Windows 2000 SP4 OS

Since the difference is not 95/98/ME vs. 2000/XP, but a 2000 vs. 2002 issue, would you try the same solutions, or is there another approach

Many thank

Jeff