[THIN] Re: AccessXP performance tweaking?
- From: "Pardee, Michael" <MPardee@xxxxxxxx>
- To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
- Date: Fri, 17 Oct 2003 15:51:22 -0400
Thanks Greg. It does seem as though the developers (internal) have kept the
forms in a smaller front end database and the data is back on one of our
clusters. I tried moving the front-end stuff down to the terminal server
but really didn't get any performance gains.
Strangely enough, we did see better results when access the back end data by
drive letter instead of UNC path, but we can't get that piece consistent.
Maybe OfficeXP didn't get installed correctly. It was our first attempt
with it after it had just come out and I believe an MSI was built that loads
most of the application. We may pull a server out of the load and do a new
install to see if that addresses it as well.
-----Original Message-----
From: Greg Reese [mailto:GReese@xxxxxxxxxxxxxxxx]
Sent: Friday, October 17, 2003 3:46 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: AccessXP performance tweaking?
I have always had odd things happen with Access apps on a terminal server.
Is it a front end back end arrangement with data and forms in separate mdb
files?
I got best results by splitting the forms and data into two different mdbs
and then launching the client side mdb with a batch file that grabs a
version from the network and copies it to their %profilepath%/Data and
launches it. I have mandatory profiles for my users so the mdb is never
there and only exists during their session. That way they don't run into
corruption issues by accessing the same front side file. It also makes
pushing out versions easy.
Greg
-----Original Message-----
From: Pardee, Michael [mailto:MPardee@xxxxxxxx]
Sent: Friday, October 17, 2003 3:40 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] AccessXP performance tweaking?
We are currently troubleshooting a performance issue with AccessXP running
on Win2k Terminal Server.
With the database on a F&P cluster in the same data center, we get query
results in 100 seconds.
Accessing the same database from a PC running Win2k and AccessXP we get
results in 40 seconds.
Move the database local to the Terminal Server we get results in 9 seconds.
We are running out of ideas and are starting the case with MS Premiere
support, but I don't know how far that will get us.
Has anyone done any tweaking to OfficeXP / AccessXP to help with
performance? AccessXP seems to be the only app showing this behavior.
Thanks in advance.
Michael Pardee
Director
Coventry Health Care, Inc.
Phone: (724) 778-3733
Fax: (724) 778-6899
<Mailto:mpardee@xxxxxxxx> Mailto:mpardee@xxxxxxxx
Email Confidentiality Notice: The information contained in this transmission
is confidential, proprietary or privileged and may be subject to protection
under the law, including the Health Insurance Portability and Accountability
Act (HIPAA). The message is intended for the sole use of the individual or
entity to whom it is addressed. If you are not the intended recipient, you
are notified that any use, distribution or copying of the message is
strictly prohibited and may subject you to criminal or civil penalties. If
you received this transmission in error, please contact the sender
immediately by replying to this email and delete the material from any
computer.
Email Confidentiality Notice: The information contained in this transmission
is confidential, proprietary or privileged and may be subject to protection
under the law, including the Health Insurance Portability and Accountability
Act (HIPAA). The message is intended for the sole use of the individual or
entity to whom it is addressed. If you are not the intended recipient, you
are notified that any use, distribution or copying of the message is
strictly prohibited and may subject you to criminal or civil penalties. If
you received this transmission in error, please contact the sender
immediately by replying to this email and delete the material from any
computer.
Other related posts:
