[THIN] Re: AccessXP performance tweaking?
- From: "Greg Reese" <GReese@xxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Fri, 17 Oct 2003 16:26:42 -0400
I doubt a consultant could do much for you. In the end they will try and
convince you it is Citrix. The trick is just getting the code refined and then
managing the files so the users don't try and lock the same file at the same
time. How much memory gets burned when the app is loaded in your scenarios?
It may just be a matter of using a more efficient data access method by the
programmers.
-----Original Message-----
From: Pardee, Michael [mailto:MPardee@xxxxxxxx]
Sent: Friday, October 17, 2003 4:11 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: AccessXP performance tweaking?
They are our own. Not directly reporting to me, but they have been OK to work
with so far. It originally started with them screaming at me about this being
a Citrix problem. Sound familiar anyone? Once I moved the databases to the
local Citrix server and it outperformed their PCs they took a different tone.
Now we are able to work together. They know we want to help them and get this
resolved quickly.
They are talking about bringing in consultants to help them with the app.
-----Original Message-----
From: Greg Reese [mailto:GReese@xxxxxxxxxxxxxxxx]
Sent: Friday, October 17, 2003 4:05 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: AccessXP performance tweaking?
I do know Access XP is better on a terminal Server than Access 2000.
Fortunately for me I was also the developer and ended up rewriting the app to a
MySQL backend and then things got really really fast.
Usually where I run into problems is when several people are accessing the same
mdb in the same location. if the mdb is in j:\apps and everyone on the same
terminal server is loading it up from that file. In access 2000 the mdb gets
shredded. XP may not be corrupting it but might be having to do more repairs
on the fly to keep it that way.
A lot of it comes down to the code. Are these your own developers who can work
with you on this or are you stuck with what you get?
Greg
-----Original Message-----
From: Pardee, Michael [mailto:MPardee@xxxxxxxx]
Sent: Friday, October 17, 2003 3:51 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: AccessXP performance tweaking?
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.
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:
