Hello Sherri,
The message is that the information is being written to work files. The reports are printed from work files instead of directly from a batch file or from the posted WIP transactions file.
These reports may be a little slow because of the volume of information that is being processed and, in spite of the message saying that the program is not responding, the program may still be working. Don?t be too quick to hit the reset. For example, I copied a batch of 1400 Time and Disbursement entries. The Task Manager says that the program is not responding but within a minute, I had 2800 entries.
When I print this sample batch, the workfile was generated in less than 5 seconds and the preview showed information within 15 seconds. I had similar results with the T&D Ledger. With 33,000 posted transactions, generating the workfile took a minute.
Here is another note regarding Adagio and Speed that was posted on the forum in March of 2002:
Over the last several months, we have assisted several sites moving to Adagio, both internally and through Softrak's Technical Support Forum, where the performance of Adagio was not acceptable.
There have generally been two environmental issues that, once identified, have resolved the problem of slowness. Firstly, many new machines come with Norton Anti-virus pre-installed, and set to check every single file each time it is opened. Given the number of files that are opened and closed in an accounting application, this brings the workstation to a halt, particularly with large databases. We have also found that, in some circumstances, simply disabling NAV (the big red circle through the icon on the system tray), does not actually turn off this behavior. To get NAV "out of the way", you must bring up the Task Manager (ctrl-alt-del), and end the task Navapw32.exe by selecting it and clicking "End Task".
We have also had several sites that are trying to run Adagio over old 10Base-T networks. Many years ago, there was not a lot to choose between the performance of the network and the local workstation in moving data back and forth, particularly under Novell. However, this situation has changed dramatically over the last few years. Your typical Windows workstation can open/close/read and write data to and from its local hard disk way faster than over "the wire". With other network traffic (e-mail and the Internet), it is not reasonable to expect adequate performance on anything less that 100Base-T networks. Also remember to check the network hubs, as these may be slowing the network down if old ones are being used. To evaluate the impact of the network on the performance of your applications, make a copy of the data on your local hard disk, and measure the improvement on an activity that takes a measurable amount of time (crediting an order with a large number of lines, or printing an Aged Trial Balance in Salesman sequence).
If you have reports that are taking a long time to print, and the data they display does not have to be "up to the second" accurate, you might consider printing these reports off a local copy of yesterday's data. They will run a lot faster.