Need to improve / shorten startup of DB

[PosseJohn]

Some of my users are complaining that the amount of time it takes to load the
DB application and associated data.

How do I improve load time of the DB?

 

[PieterLinden via AccessMonster.com]

Some of my users are complaining that the amount of time it takes to load the
DB application and associated data.

How do I improve load time of the DB?

My car doesn't accelerate very well... how can I fix it?

That's a really vague, generic statement....

How about a little information... WHAT exactly doesn't load quickly? Do you
have forms bound to unfiltered tables? There are lots of things you can do
to throttle a database. Exactly what isn't working well?

 

[JimBurke via AccessMonster.com]

One thing you should do is step though the code in the startup process and
see if you can pinpoint where the slowdown occurs.

Do you have linked tables? If so, do you always run the code to link them?
You should re-link the tables only when you are implementing changes, either
to the front end and/or back end. re-linking can take a fair amount of time.

Are you running in a server environment? There are several things that can be
done to improve performance when running with the back end on a server. I
don't remember them offhand, but if you do a web search you should find a few
recommendations for what can be done.

Do you regularly compact/repair and decompile your appl? I had a performance
problem back when I didn't do this - over time DB bloat can have a big effect
on performance. If you haven't been doing this I would try this right away.
Compact and repair alone doesn't do it, you also should decompile regularly.
I always compact/repair, then decompile, then compact/repair again. This keep
the appl DB size to a minimum. The back end DB can be compacted as well, no
need to decompile it, but I don't think that has much of an effect on
performance as opposed to the front end.

 

[David H]

Everything else notwithstanding, keep in mind that 'slow' is all subjective
and that there are usually person's within an organization that consider 5
seconds 'slow'. While looking for potential bottlenecks in the startup
certainly isn't a bad idea, temper the comments against the reputation of the
people making them as well as the feedback from the other users. Also, if
your environment is a mix-mash of PC's it might be that its something related
to the person's PC.

Also, do you have some sort of progress meter or form that displays the
startup status? Adding one that gives the user information on the startup has
a magical way of improving the startup speed even when you haven't changed
any of the code. Its a psychological thing.

 

[Tom van Stiphout]

On Sun, 16 Aug 2009 14:04:41 GMT, "JimBurke via AccessMonster.com"

That is NOT a recommended procedure. This option is undocumented for a
reason.

-Tom.
Microsoft Access MVP

 

[JimBurke via AccessMonster.com]

What's the problem with decompiling? I had serious performance problems and
bloating before I started doing this, decompiling took care of it. Been doing
it for the last four years. Is there an alternative?

 

[Douglas J. Steele]

You may want to read what MichKa has to say about decompiling at
http://www.trigeminal.com/usenet/usenet004.asp

 

[Dale Fye]

Is your database split?

If so, does each user have their own front end on their PC?

If not, you need to split it, put the data on a shared network drive, and
give each of your users their own copy of the front end (installed on their
PC).