Split Database Slow response time

C

ConfusedCraig

Small database, small tables, few users. B4 tables and forms,reports all in
the same database;response time 1-3 seconds. After split(tables in separate
DB) and link to tables from application DB; slooooooooooow. 30-45 seconds vs
1-3 seconds. Both before & after Data and Apps on a network server. Is there
some parameter that can be set to not pay the Linked file response time
penalty?
 
J

Jeff Boyce

If I'm interpreting your description correctly, you have the application
(front-end) AND the data (back-end) both located on a network server. This
would mean that every time a user on a PC wants to open a form, s/he has to
get it downloaded over the network to his/her PC. Tremendous network
traffic and slow response!

What happens if you put a copy of the front-end on a PC and link to the
back-end tables/db? (By the way, this is the preferred design/use of a
"split" db.)

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
T

Tony Toews [MVP]

ConfusedCraig said:
Small database, small tables, few users. B4 tables and forms,reports all in
the same database;response time 1-3 seconds. After split(tables in separate
DB) and link to tables from application DB; slooooooooooow. 30-45 seconds vs
1-3 seconds. Both before & after Data and Apps on a network server. Is there
some parameter that can be set to not pay the Linked file response time
penalty?

As Jeff states you really want to give each user their own copy of the
FE. I specifically created the Auto FE Updater utility so that I
could make changes to the FE MDE as often as I wanted and be quite
confident that the next time someone went to run the app that it would
pull in the latest version. For more info on the errors or the Auto
FE Updater utility see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the
FE on each PC up to date.

However there are other things you should do to speed up your response
time.

The three most common performance problems in Access 2000 or newer
are:
- LDB locking which a persistent recordset connection or an always
open bound form corrects (multiple users)
- sub datasheet Name property set to [Auto] should be [None]
- Track name AutoCorrect should be off

If the problem is for everyone when starting up the MDB then it likely
needs a decompile.

For more information on these, less likely causes, other tips and
links to MS KB articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

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/
 
T

Tony Toews [MVP]

Jeff Boyce said:
If I'm interpreting your description correctly, you have the application
(front-end) AND the data (back-end) both located on a network server. This
would mean that every time a user on a PC wants to open a form, s/he has to
get it downloaded over the network to his/her PC. Tremendous network
traffic and slow response!

That might not be so bad actually. A client was running that exact
environment on a Terminal Server/Citrix environment. They didn't want
to copy the FE onto the Terminal Server system so I created individual
FE folders on the file server.

It may have been slightly sluggish compared to a local copy but it
worked well.

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/
 
C

ConfusedCraig

B4 the split tables and forms were in the same data base, but the database
was on a server on the network. Why does linking to tables in another
database affect the time it takes to load a form ?
 
T

Tony Toews [MVP]

ConfusedCraig said:
B4 the split tables and forms were in the same data base, but the database
was on a server on the network. Why does linking to tables in another
database affect the time it takes to load a form ?

See my other posting. Or visit the Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

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/
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top