05-25-2011 07:00 AM
We have installed ACT 2000! on our new Windows 7 32-bit systems without any problems. After the installation, we ran into the following issues:
Already documented was Office 2010 not being compatible as a word processor. I converted our fax cover sheet over to the ACT word processor, which works fine. However, the user has to have admin rights on the PC in order for it to work. Using the "run as administrator" option works, but it then requires the admin password. Our users are power users on the desktop, so not a feasible work around. Research on Microsoft's site doesn't come up with any way to embed that information in the startup and only yields shutting down UAC, which is just as unworkable.
Prior to Windows 7, we had the database on the Netware server with multiple logins and generally 4 people were in the database at one time. Windows 7 will never load the network database if somebody else is using it. In testing, as soon as the current user exits, the next user can login. We have had to redesign our "sharing" system.
05-25-2011 07:15 AM - edited 05-25-2011 07:16 AM
Welcome to the Sage ACT! Community. Usually disabling UAC (which most users find to be more of a hindrance than a help) will resolve access issues in Windows 7 and Windows Vista. When you say doing this is "unworkable", does that mean it did not resolve the issue or it is something you do not want to do?
Note: Effective 6/1/13, Sage no longers provides support for the Act! software. This is now provided by Swiftpage.
05-25-2011 07:42 AM
05-25-2011 08:53 AM
I did some quick research on opportunistic locking and it appears there are limitations to disabling opportunistic locking on the later server editions and Vista and Windows 7. If true then ACT! 6 and before must be considered totally incompatible with the later Windows operating systems.
05-25-2011 09:09 AM
05-25-2011 09:23 AM
what I found was here http://support.microsoft.com/kb/296264
I didn't try to digest the whole thing but where they were discussing SMB1 and SMB2 looked critical.
05-25-2011 09:38 AM
05-25-2011 09:42 AM
When our Power Users attempt to use the Write feature of ACT 2000!, they get the message "failes to connect to word processor: act word processor" and behind that window is the message "wp driver is not running"
As for the multiple logins, if one user is logged into the shared database (software on workstation, database on network), it loads about 11% and then stops. No error message. Just never finishes the load.
05-25-2011 09:51 AM
For the WP error, see this ACT! Knowledge Base article -
For the 2nd, maybe these:
The 2nd one refers to issues with old versions of Netware... not sure if still relevant