Slow to open reports in design view

[Mike]

We have an Access 2003 database (used as a front end
to a SQL database) with 400 reports. Recently, when opening reports in design
view, I receive the message that the report was not formatted on a certain
printer and would I like to use the default printer. The first printer is a
non existent former Network printer and the reports take forever to open in
design view. (We made the network change in printers quite sometime ago, so I
don't know why this came up suddenly). What's more is that in production when
a user prints a report, the application first opens the report in design view
to add a tag. So, we are experiencing serious performance problems for our
users. Any ideas on how to programmatically modify the printer that the
report was formatted with? I really don't want to open each of the reports
and click yes to the prompt for changing printers. And then of course, what
happens when we get a new printer? As I mentioned, this started happening for
no obvious reason a couple of weeks ago. Any help or suggestions would be
appreciated.

 

[NoodNutt]

Mike

Just a few of thoughts:

1. Do you compact on a regular basis, if so Daily, Weekly or monthly?

2. The queries in which all the report are based, are they nested, do they
entail alot of criteria and WHERE clauses?

3. How many same/ or different reports are being accessed simitaneously?

4. How much memory power does the main server have, in addition, each
worstation have.

The Company I work for just spend a boat load of $ upgrading the entire
network because of this, new mainframe servers; Each of our workstations now
boast 1Gig Ram, which maybe overkill, and the main servers have their
memslots maxed to help with any excess load problems.

So far I have not experienced any of the previous problems, Yet!

Nothing exceeds like excess, better to have too much than not enough.

Good Luck

HTH
Mark.

I should imagine, with 400 nested reports with mutiple criteria's having to
re-calculate/refresh each time new records are added to the Back_End which
(correct me if I'm wrong, would be sizable) it would have a slowing affect.

As I stated, just thoughts, hopefully they will help.

Mark.

 

[Mike]

Thanks for your response.

Yes, we compact regulary.
No, the reports do not use nested queries.
The user base is small (<20) so not a lot is happening simultaneously.
Our SQL server has plenty of juice.

Additional info:
After opening a report in design view, and answering the prompt about
formatting to the new printer, and then saving the report, the report
functions as it always has. So, I assume the problem is related to a search
for a non existing network printer.

Also, based on reading other posts related to similar sounding problems, I
have turned off the Name AutoCorrect feature.

mike