REPORT WAIT TIMES
We have a commercial accounting software package programmed in Access. Recently began having to wait for some reports to process to the screen for over 3 minutes. We have only had this software for under a year and have eliminated the problem being the network by moving the data files from the server to the desktop and running the reports there - no difference.
Developer tells me that the only changes they've made to the structure of the reports is to make them "SQL Server ready" for future use. Could this change cause the sudden slowing of report processing?
We are now looking at upgrading our workstations of course, but I'm wondering why this problem just suddenly showed up instead of a gradual slowing down over time as the amount of data in the tables increase?
Software/Hardware used:
Software/Hardware used:
ASKED:
March 30, 2005 10:28 AM
UPDATED:
March 31, 2005 9:13 PM
Answer Wiki:
It would be interesting to know what kind of things would need to be changed in reports to make it SQL Server ready. Reports are based on queries or tables. Queries are based on table. Tables are either native Access, linked using ODBC or OLE datalink. But to Access reports, all these types of tables would look like the table is in Access. Anyway, assuming that the tables are still native Access tables, have you tried compacting the database? That usually dramatically improves the performance. Also, sometimes there seems to be that magic number of records that once a table reaches that point performs poorly if it is not indexed properly.
To see all answers submitted to the Answer Wiki: View Answer History.
How long have you had this accounting package. I know older versions of access had very attainable limits to the database size. Once these limits were reached it literally would be a sudden drop. The company doing these reports might have already been aware of this and used the ?SQL ready? reports as the plant for a future upgrade you may have to undertake.