After a recent upgrade from Access 97, all my queries which use dlookup now take about five times as long to run. Is this to be expected in 2000? The use of dlookup was inherited, but it's pretty intrical, so I’d hate to junk it. Any ideas?
I had a similar performance issue shortly after converting my Access 97 database to 2000. After a couple of re-compiles, the performance issues, broader than the Dlookup one, went away. WEIRD!
You could try that. Otherwise, on a technical level, I don't know.
It's a function of "bloat" that is inherent in A2k and the overall slow processing of domain aggregate functions in general. Domain aggregate functions are notoriously inefficient methods in Access. So much so, that there have been other domain aggregate functions written by other people for this very reason.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.