Wow, this is a big question, Janis.
It will be a matter of tracking down *what* is slow, and addressing that.
A2007 is slower, as new versions usually are. But it should not be
impossibly slower.
You've been posting here for a while, so you probably know about Tony's
performance FAQ for Access:
http://www.granite.ab.ca/access/performancefaq.htm
There's lots of important info there: name autocorrect, subdatasheets,
length of path names, and so on. You probably also have the database split
so each user has their own front end on the local hard disk. And presumably
this is in a trusted location.
To track down why it's slow, you might start wtih a simple, new, codeless
form, bound to a table/query that runs well, so the form opens almost
instantaneously. Then start adding suspect stuff to see what slows it down.
Divide'n'conquor, i.e. take half the stuff and figure out if that's the fast
half or the slow half; repeat until you pin the culprit(s) down.
Presumably you do have SP1 applied:
http://office.microsoft.com/search/redir.aspx?AssetID=DC102486291033&Origin=HH102511011033&CTT=5
It is possible to get A2007 running well. Just tested, and it takes less
than 2 seconds to load a form with 12 subforms and 26 combo/list boxes
(including those in the subforms.)
Can understand your frustration when you have lots of apps to test. It will
need some dedicated time to pin down the bottlenecks and find alternatives
for those things.
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Reply to group, rather than allenbrowne at mvps dot org.
message
news:
[email protected]...