Making Access go faster

T

Timboo

Hi there, I have just split my database so that the tables are located on the
network drive, and the rest runs locally. However I am finding that the
forms take a while to load, since doing the split, and this is when the
database only has test data in it. Is there anything I can do to speed up
access? I admit my basic (long winded)program skills probably account of a
huge overhead! Thanks Tim
 
I

ILuvAccess

Not to sure if this may totally solve your issue, but you may want to try and
"Compact and Repair Database....." your database. Select Tools/Database
Utilities/"Compact and Repair Database..."
 
P

pbrstrtgang

Hi there, I have just split my database so that the tables are
located on the
network drive, and the rest runs locally. However I am finding
that the
forms take a while to load, since doing the split, and this is
when the
database only has test data in it. Is there anything I can do
to speed up
access? I admit my basic (long winded)program skills probably
account of a
huge overhead! Thanks Tim
..


How about Compact and Repair?
..
 
T

Timboo

Thank you to all for your comments, yes I have done a compact and repair
(amazing what space you can get back). I dont think the network traffic is
bad, other activities such as file transfer seem acceptable. The forms are
taking about 2 seconds to load, when locally based they took fractions of a
second, so you only saw a flicker betweeen each form opening. They do have a
number of controls on the form, (no images, or very complex queries) as the
subform is continious, there can be up to 300 items displayed, but again when
local to the pc, even these forms opened quickly. Perhaps rather than close
forms and open a new one, I should minimize all of the forms and then
maximize the desired form. But is this good practice? Thanks Tim.
 
A

Albert D.Kallal

To get the performance back, you need to use the persistent trick.

This trick simply means that you in the startup of your database open a
connection to the BE file, and KEEP it open.

This can "keep" or force this connection open by either opening a form
attached to a table, (and then minimize it), or simply have some code that
opens a table to a global recordset....

doing the above should restore performance back to un-split rates....
 
Top