Access running slowly over Network

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am using access 2003 over a network

The Tables are contained in a MDB file located at a WinXP Server. There are few thousand records in the tables
And at each workstation I place anther MDB file which contains the Queries, Forms and Macros
The workstation mdb files are linked to the Server mdb file

At workstation A when I open a form, query or table, it takes few seconds to have the datasheet or form displayed

Before the form at workstation A is closed, I move to workstation B and to open a form or query, now it takes very long time (more than 20 secs, sometime a min) to return me the datasheet or form

In my office set up there are around 5 workstations working on same database at the same time. Pls advise how to set up my database programme to achieve a fast response time

Pls also note
My WinXP server is WinXP Professional, 512M Ram, P4 2G Hz
My workstation are Win98, 128M Ram, P3 766 MH
 
Try the following trick:

When the application loads, have your code open some table from the back
end...any table will do.

If you *keep* or force the connection open at a all times..then that delay
should go away...and often you get even BETTER performance then even the
"few" seconds that original form takes to open.

For a list of things to check..and including the above trick...check out:

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

You also should consider placing mde's on each computer in place of a
mdb....
 
Dear Alber

Thank you for your quick response. I have tried what you suggested and the outcome is amazing. I first open a small table which took long time (more than one minute), but after keeping this table opened, I switch to other operations, opening form and queries and the loading times are much much faster, even with my Win98-766MHz 128M Ram, workstation the response time is within 2 secs, and on my another WinXP (Home) workstation the response is instant. Thank you for your great suggestion

Meantime would like to ask further

Does this "trick" have any adverse effect / any downside

You have suggested mde in replacement of mdb. Can you tell me what is "mde"

Best regard
Simo


----- Albert D. Kallal wrote: ----

Try the following trick

When the application loads, have your code open some table from the bac
end...any table will do

If you *keep* or force the connection open at a all times..then that dela
should go away...and often you get even BETTER performance then even th
"few" seconds that original form takes to open

For a list of things to check..and including the above trick...check out

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

You also should consider placing mde's on each computer in place of
mdb...
 
Simon said:
Does this "trick" have any adverse effect / any downside?
Click to expand...

No, the trick does not. In fact, it actually reduces bandwidth..as a whole
bunch of re-opening, and re-connecting to the ldb locking file is
eliminated by doing this trick. So, no...it is good thing, and it reduces
systems loads..and makes your application run better. I don't know of any
real downside.

In place of opening a table..you can even open a form..and minimize it to
get the same effect.
You have suggested mde in replacement of mdb. Can you tell me what is
Click to expand...
"mde"?

A mde is essentially a "production" version of your application. All the
code is compiled, and all code source etc is stripped out. It is much like
creating .exe file. It is the "final" result. You users (or clients) will
NOT be able to modify this resulting file (nor will you...so MAKE SURE you
keep the original mdb file that you use to make the mde). As a general rule,
only your front end needs to be a mde. This mde is thus then place on each
pc..and design changes cannot be made to it (so, it is a good safe way to
protect your designs also).

Since the code is compiled, then problems of application load time, or even
some code becoming un-compiled cannot happen. You will as a general rule
find your application also runs a bit more snappy. Even more important is
that any un-handled error(s) do NOT re-set all your global, or current
variables in scope. So, this also makes your application far more reliable,
as an un-handled error does not clear your variables.

Don't know what version of access you are running..but check the help on a
mde.
 
This is great info out of the trickbox. Question:
Theoretically, if I use the default Access Switchboard as
the Main Menu, I could leave the Switchboard items on the
Server BA, Link the local FE to that Switchboard Item
table, and voila, this would do it since the Switchboard
is open during the whole session. Is my logic right?
Brigitte P.
 
Back
Top