ACT 2012 Housed Database got a New Computer

[HeatherJoy75]

My current computer has limited RAM so I have purchased a new computer for my desk.  My computer houses the database we use for the office.  I only have 2 liceses for the office.  As soon as I installed ACT! 2012 and the databases on the new computer, I was able to access it but with limited functionality and the second user, who is in another office, cannot locate the database any longer.  The computer is named the same, and the file is in the same path location, however, it is no longer allowing me to "Share" the database.  It is greyed out and does not allow me to change anything even if I attempt to run as an administrator.  We had many problems when we first installed the ACT! program in August 2012 and clocked many hours with the ACT! tech team.

I have since gone back to the old computer to conduct business, but that computer is going to crash at any time and will make this move to the new computer manditory.  Our business demands the use of ACT! on a 24/7 basis until we find a suitable program with less issues so we cannot afford more than a couple hours downtime and that is only on weekends. This problem also alerted me to the fact that ACT! support does not work weekends or after typical work hours.  Any suggestions?

[ghollister]

Hello Heather,
Welcome to the Sage ACT! Community. Please see the following Knowledgebase articles for suggestions to resolve this issue:
http://kb.Sagesoftwareonline.com/cgi-bin/Sagesoftwareonline.cfg/php/enduser/std_adp.php?p_faqid=2423...
http://kb.Sagesoftwareonline.com/cgi-bin/Sagesoftwareonline.cfg/php/enduser/std_adp.php?p_faqid=2281...

In addition, if the new machine is Windows Vista, Windows 7, or Server 2008, try disabling User Account Control:
Windows Vista: http://kb.Sagesoftwareonline.com/cgi-bin/Sagesoftwareonline.cfg/php/enduser/std_adp.php?p_faqid=2022...
Windows 7, Server 2008: http://kb.Sagesoftwareonline.com/cgi-bin/Sagesoftwareonline.cfg/php/enduser/std_adp.php?p_faqid=2566...

One other possibility might be an issue with your Windows profile permissions. Ensure that your Windows account is only assigned to the Administrators group and no other groups (i.e., Debugger Users, Users, etc.)