By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,694 Members | 2,015 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,694 IT Pros & Developers. It's quick & easy.

Does Converting From Access 97 to 2000 Slow Down Existing Code?

P: n/a
Greetings,

The subject says it all. Certain operations that used to run pretty
fast in A97 take noticeably longer after converting a database app to
A2K.

For example, during login process the code checks for existence of two
tables and whether they contain any data. Took 2 seconds, now takes
15-20 seconds. A report based on multiple SQL statements in each
control source took 5 minutes, now takes an hour.

I thought A2K was supposed to be more efficient in such things. Has
anyone here experienced similar problems, and is there anything I can
do to address them?

Thanks,
Yisroel
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Access 2000 will not be faster than A97, but it does not have to be much
slower.

Take a look at the Performance FAQ by Tony Toews at:
http://www.granite.ab.ca/access/performancefaq.htm
and work through the issues listed there.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Yisroel Markov" <ey*******@iname.com> wrote in message
news:2f**************************@posting.google.c om...
Greetings,

The subject says it all. Certain operations that used to run pretty
fast in A97 take noticeably longer after converting a database app to
A2K.

For example, during login process the code checks for existence of two
tables and whether they contain any data. Took 2 seconds, now takes
15-20 seconds. A report based on multiple SQL statements in each
control source took 5 minutes, now takes an hour.

I thought A2K was supposed to be more efficient in such things. Has
anyone here experienced similar problems, and is there anything I can
do to address them?

Thanks,
Yisroel

Nov 13 '05 #2

P: n/a
> 15-20 seconds. A report based on multiple SQL statements in each
control source took 5 minutes, now takes an hour.
I'm particularly interested in that.

If you get a chance, could you post back on how that report
runs after you've applied the optimisations listed at Tony's
site?

(david)
"Yisroel Markov" <ey*******@iname.com> wrote in message
news:2f**************************@posting.google.c om... Greetings,

The subject says it all. Certain operations that used to run pretty
fast in A97 take noticeably longer after converting a database app to
A2K.

For example, during login process the code checks for existence of two
tables and whether they contain any data. Took 2 seconds, now takes
15-20 seconds. A report based on multiple SQL statements in each
control source took 5 minutes, now takes an hour.

I thought A2K was supposed to be more efficient in such things. Has
anyone here experienced similar problems, and is there anything I can
do to address them?

Thanks,
Yisroel

Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.