08-12-2014 02:32 PM
We're a sales office of 3 people using ACT Pro 2011 v 220.127.116.11; shared database on a machine running Windows XP (I know!) ACT has a tendency to "think" a lot, being that sometimes it take more than a few seconds to respond, but it can take as long as 30 seconds to access the Task List and often times locks up complete (to the point of needing to be restarted) when Scheduling an Activity. Any insights into what's causing this will be helpful.
08-12-2014 03:02 PM
How much RAM do you have on the XP box with the database? XP did have an option to use 3-gig of RAM when operating as the server. I suspect that the server is needing to do significant use of virtual memory (hard drive) to perform tasks such as assembling the task list. Basically it's not the ACT! program but the SQL server that's taking the time.
08-12-2014 09:52 PM - edited 08-12-2014 10:13 PM
i assume all users are in a lokal network? (no vpn envolved?) if you have a local network delay this can exactly cause this kind of delays.
other than that, i created a KB entry that shows most reasons for a delay while accessing the ACT database
08-13-2014 07:45 AM