Slow startup of access applications

[Guest]

Hi newsgroup

Since we switched from NT4 (with Office XP) to WinXP we are experiencing
that Applications based on Access take a much longer time to start than
before. In the newsgroup I read something about a table property "sub
datasheets" that can be set to "none". Any other good ideas?

Any Input is highly appreciated.

Kind regards
Gabriel

 

[Albert D. Kallal]

You don't mention if you have a split db, and you don't mention if you have
multi-users.

The #1 solution that fixes this problem is a persistent connection. That
means at the start of your program, you open a table, and keep that table
open. This 9 out 10 times fixes the slow form open problem. So, try this
first.

The best list of things to check can be found here:
http://www.granite.ab.ca/access/performancefaq.htm

Go through the above list...and I am sure you will fix your problem(s).

 

[SJ]

I've also found that our Access DB's slow down too. At first I thought I
tracked it down to a lot of data in a hidden table MSysCmdbars or something
like that as we build and drop menus as we fire up. So I put some code in
to clean that up. Actually I found that I could only delete the records via
a query, not in datasheet view.
These days the things just become slow to start. So now I rebuild them
when they get slow.. Create an empty db, import your object, set the
references, menus etc, maybe keep a template for doing this with
references menus in it etc, then import the objects. You'll be surprised
at the results....

 

[SJ]

The other thing I forgot to mention. when you create a new db, tools
options turn off auto name correct , the 1st thing you do. You don't
need it and it just bloats the db...