05-28-2009 03:14 AM
We have ACT by Sage 2007 (9.0) Version 18.104.22.168, Hotfix 1, English (United Kingdom) and also Sage Line 50 Accounts version 12.01.0034. We have recently had an issue where the users’ search windows hang or pause for around 10 to 15 seconds or so. The Act windows do not completely clear, as if the PCs CPU is running at 100%, which it isn’t, and the next window with the customers information on it does not draw or fill with details clearly until this delay has passed. Once at this point, there is much less slowness using Act and Sage together to create orders or invoices.
We run the Act SQL server on an IBM Eserver with a 3Ghz Xeon CPU running Windows 2000 Server SP4 with about 2GB of RAM, and it has proved perfectly adequate as there are only 5 users and about 13,000 records in the database. It links to Sage Line 50, based on another shared drive on the same server, with the ‘Accounting Program’ tab in the Act record, from which the users create new records and orders. This system has been running perfectly quickly, with almost instantaneous responses for about 2 years.
This happens on every search but is worst on a post code search, which is unfortunately the users’ initial process. The users first response to an incoming telephone call is to look up the customer on the database by post code, and this has started to impact the usefulness of Act in that the users have to tell the customer to wait until the system 'catches up', and brings up the customers details. This can take from a few seconds to more than 20 and has become a major issue.
We recently had a problem where Act was crashing a few times a day on every PC, after some Windows Updates were installed, but when a procedure outlined on this forum was followed, uninstalling Dot Net 2, 3, and 3.5, then reinstalling only Dot Net 2 from the Act CD, this problem was resolved. However, the slowness and window hanging has continued to adversely affect the users.
Any assistance much appreciated….
06-02-2009 08:20 AM
Do you get the same performance when doing lookups in the local demo database? You can also try clearing the MRU drop-down list for lookups.