"hs***********@hotmail.com" <hs***********@hotmail.com> wrote:
Instead of measuring time interval between command button clicks, I'd
like to measure the time interval betweeen when the application (.mde)
is opened, and when the main form's Activate event occurs. I am trying
to measure, diagnose and fix system slowness.
When was the last time you did a decompile?
Decompile or how to reduce Microsoft Access MDB/MDE size and decrease start-up times
http://www.granite.ab.ca/access/decompile.htm
Alternatively are you relinking tables to a backend MDB at startup? If so open a
recordset against the first table once you've relinked the first table. Relinking
of the subsequent tables will be much faster, especially if someone else is already
using the backend MDB.
Finally 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 
