I would like to suggest a Forum within the Community to place common problems that are arising specific to an ACT! Version which can quickly highlight issues which are affecting Users and their ability to manage their database content.
At present there are a few Known Problems with various versions - some with Workarounds and others, while perhaps not critical show stoppers, are causing problems for ACT! Consultants and Users with no clear guidance from the KB. Looking up the KB for the Error Message does not find the message let alone the answer. Sometimes the KB is focused on a key word and produces a result covering almost the entire KB ID list.
The current KnowledgeBase is not User Friendly! It does not focus on ACT! User Requirements and seems to get cluttered with answers relating to other Sage Products (such as Peachtree) which have no relevance to the ACT! Issues being researched; or, is padded out because the fuzzy search result picks up ACT! or History etc from the phrase and offers options covering some 60 or more pages to search through. Certainly not as friendly as the old KB.
Some are issues are integral problems to ACT! - others appear to be generated by Microsoft Updates and/or issues with integration of WIn 7 or Office 2010 - but are nevertheless worthy of note.
There is the Problem associated with the Calendar / Date Time Setting in some parts of the world that has not yet been addressed in a Patch nor included in the KB - but has now been remedied through a workaround to change the Time Option from a.m./p.m. to AM/PM. - there were several threads the Community Forum addressing the same issue but not necessarily linked to a common thread.
Another recent Bug to appear is the missing History Tab options when an ACT! 2011 database is created from a copy ( Empty or Otherwise) - This is the " InvalidArgument= Value of '-1' is not valid for 'index" - Parameter name "Index" issue".
My Current Workaround
I have found that creating a new database on the same workstation will generate a database with all features in place. Only problem then is to use the client view template and recreate the fields in the database before importing a CSV Version of the database or in some cases an import will work.
Problem- It does not address the issue of how to fix the active database missing history types. Replacing Preferences doesn't work! The problem can be triggered on a perfectly good database where the is a syncronisation in place and the synchronising RDB triggers the failure in the Master Database.
I believe we need a single reference point for Bugs to be reported and commented on by the Sage Moderators/Experts rather than hunting through the many posts to find the issues and "what" action is under way by Sage Support expertise for guidance or a Quick Fix to help the Users.
Sending the anonymous error reports from within ACT! when they popup is fine - but how do we know how many people are affected and possible causes?