Delayed Response from DB on Server

[Maureen]

HELP PLEASE! I have developed an access '02 DB, split
front end and backend. Created on Windows XP PC. It is a
large application and some forms take 10-12 seconds to
open on my PC - this is tolerable.

Problem I am encountering is when I put this DB on a
Windows NT server and access it using Citrix, the
response time for overall DB usage is severly
compromised, example being one form in particular takes
90 seconds or more to open. The Access program being
used is Access 2002 - same version used for development
although a different installation.

Anyone have any ideas/suggesions/solutions???? What
could be causing the excessive delays when this
application is run on a network? Could it be the
network? Could it be the Access installation on the
server? Could it be something in my db
design/development that is causing the delays?

Any help will be most appreciated!!! Thank You!

 

[Nikos Yannacopoulos]

Maureen,

I couldn't tell you much on the Citrix case, but 10-12 secs on an NT Server
sounds a lot anyway, so it may be worth having a look at Tony Toews' page:

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

It helps you improve your db performance enormously, and hopefully that will
also apply in the Citrix server scenario.

HTH,
Nikos

 

[Maureen]

THANKS Nick. I have visited Tony's pages - great stuff
but I still needs some help. Everything on the db is
slower in the NT Network/citrix environment - especially
the one form I mentioned previously. In addition to
working on improving the form performance (which I am
pursuing) can anyone offer any additional
insight/suggestions???

 

[Albert D. Kallal]

THANKS Nick. I have visited Tony's pages - great stuff
but I still needs some help. Everything on the db is
slower in the NT Network/citrix environment - especially
the one form I mentioned previously.

In other words, you have tried some of the suggestions at Tony's site and
noticed a big increase in performance? (what did you try, and what gave you
the most increase in performance?).

I will say that right now that keeping a persistent connection opened form
the back end to the front end is likely the best trick Tony has. In my
experiences (and using Citrix), this trick alone restored performance to
EQUAL that of running without NO network. So, I would much suggest you try
some of those suggestions.

Further, I assume you are running a split database, and despite using
Citrix, each user that logs on STILL gets their own copy of the front
end..right? (that means that the front end is on the Citrix server..but each
user STILL gets their OWN COPY). You also STILL MUST try the persistent
trick (did you?).

I would also as a suggestion make sure each user gets a mde for their front
end.

And, no..the network is likely NOT your problem, especially if the access
application + database both reside on the Citrix server (if that is the
case..then you network is NOT to blame).

 

[Maureen]

Thank you Albert

I have done the following in an effort to improve the
response time of the database:

1. On the largest, most complex form, which was taking
about 10-12 seconds to open on my PC; and nearly 2
minutes on the server...I removed the sourceobject of
several subforms so that they do not open with the form
but only when a tab/page is clicked on - this resulted in
an increase in response on my PC but no notable
difference on the server

2. I created a single field table in the backend -
created a form for this in the frontend and keep it open
(persistent connection open to the back end). This did
not result in any noticible improvement.

Any other ideas?