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

Access 2003 Reports slow

P: n/a
Whenever I work with reports in 2003, there is this excruciating 30 delay
when I open the report or whn I change something in the property sheet. I
have a report with three controls and no record source and it even happens
there. This only happens in 2003 and I've had the same problem with
different mdbs on different machines running either Windows 2000 or XP.

I've turned off the "Track Name AutoCorrect Info" It only happens on
reports and never on forms.

Does anyone know why this delay happens?

Thanks.

Matthew Wells
MW****@FirstByte.net
Oct 15 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Is your database split, is a network involved?

If yes to above, try opening a table (from the front end)....any table will
do. Now, minimize this table, and then try working on the report....notice
how your delay is gone?

Another possible problem/got ya is a network printer, or a printer is set
for the report that don't exist. Again, ms-access gabs (or tries to) grab
information about the printer for layout. (so, change your default printer
to a local printer. I have a default pdf printer that I always use for
reports. This thus eliminates the delay problem, especially on my notebook,
and I am NOT connected to the office network (and, thus no printers are
available).

Check the above (I not aware that a2003 is any worse, or better in then
a2000, and a2002...as far as I know, they all perform the same).

If none of the above helps, there is list of things to check here:

http://www.granite.ab.ca/access/performancefaq.htm

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
Oct 15 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.