SAGE ACT! 2012 Data Corruption Has Me On Edge

Update 14JUN12: Sage ACT! found that one errant ical calender entry for a recurring meeting corrupted the database and rendered the synchronization functions and more unusable in ACT!  I told them to take their time studying this problem and a possible fix to make ACT! (and me!) less exposed to this problem.  They agreed. It didn’t take long to identify the problem which is really good. Sage ACT! takes this seriously–I’m happy for that.  Too many companies are firewalling themselves off from customers in this day and age.  Sage ACT! is not one of them!

Update 12JUN12:  As a result of the blog post below, I’ve now been contacted by several people from SAGE ACT! and an independent consultant who works with SAGE ACT!  SAGE ACT! has requested and will receive my full database offering them the possibility to understand what occurred to corrupt my database. I’m happy for this collaboration with them.  SAGE ACT! is responding the way great companies should respond in this situation.  I’m happy for them reaching out to me.  I will update this post as the situation unfolds.


At some point during the past couple of months, my SAGE ACT! 2012 database became corrupted. As I have been in the process of moving from one laptop to a new laptop, I had stopped using ACT during this migration period.

What’s the impact? This corruption no longer allows for the proper synching of my ACT Database with Google Gmail, Calendar and Contacts.

ACT Support informed me that some (recurring?) corrupt calendar entry from Google Calendar corrupted my entire database. The impact is not that that record didn’t make it over to ACT–I can no longer schedule anything in ACT based on a specific time and can’t synch my ACT database with Google.

This functionality worked well for about 6 months. Now, poof—it’s gone!

I’ve been using ACT since the late 1990’s—I’ve been very dedicated to this solution. Until now.

I spent considerable effort this week rebuilding an updated ACT database that I can synch with Google again. But, should I?

The data integrity between ACT and Google isn’t bullet proof. As my good friend Dave Wilkinson of DataComCorp and I discussed, it isn’t a matter of “if” this will happen again, but, “when.”

And, to determine that it has happened means I will have to meticulously back up by date and time, set up tests to determine if everything continues to synch properly, etc. In other words, I have a lot of work to do to validate that the solution I paid for is working properly. That is too much effort in my book.

What’s wrong here?

  • ACT should have better error detection and not accept records into it that can corrupt an entire database.
  • ACT alleges that this problem originates within Google and I have to accept their representation that this is true—it’s too easy to blame a third party for problems in your product., particularly when that third party isn’t involved in trouble-shooting and problem resolution.
  • ACT informs me that this issue is very rare. Can I bet my business that this “rare occurrence” that has already happened to me in the first 6 months of use won’t happen again? Simple answer: No.

I was told I could send my database into ACT to see, if, on a time and materials basis, they could determine where the problem occurred. No guarantees of success. No time or cost estimate.

Personally, I’d be happy to send my entire database to the ACT development team so they can look at it and determine what they need to do make their product more robust. No one asked for that. Blame has been assigned to Google. The matter is closed as far as ACT is concerned.

How many other customers have this vulnerability and don’t know this? How many other customers may be unaware that this has already occurred to them? After all, there is no error message being passed when this occurs. The functionality just stops working.

I really like ACT. I’m deeply disappointed that I can no longer use this product as it was intended. I upgraded my ACT version specifically for this integration with Google. My confidence is shot.

Dave Gardner, Gardner & Associates Consulting

© 2012 Dave Gardner All Rights Reserved



5 Responses to SAGE ACT! 2012 Data Corruption Has Me On Edge

  1. Dave, I have had my ACT calendar corrupted before as well but by another product. When you have two systems with totally different calendar backends trying to communicate with each other, you open up Pandora’s box. I am not defending Sage ACT, but just saying there are variables involved which make it more complex that it should be. Call Sage back and ask for an escalation the situation. Check your email – I sent an email to you via your website..


  2. I apologize for the experience you’ve had. I will discuss your case with our support team and we’ll follow up offline with more assistance. Thank you for choosing Sage.


  3. Tawny Mergel says:

    Dave, thanks for bringing this to our attention. Again, sorry that you have encountered this issue. As I mentioned on the phone, I have escalated this issue to our product development and support teams and was happy to hear when we spoke this afternoon that our Product Specialist had contacted you and will be working on your database. Please let me know if we can be of further assistance.


  4. pregen says:

    Cool indeed. Thanks Sage!


  5. Banachek says:

    Same problem and even worse,

    I lately started to get error messages when opening act. Always get one when opening or closing the calendar. It appears to be getting worse as I now get error messages when I go between calendar and database.

    Can’t open calendar without hitting something other than contacts, like Tasks.. then it opens.

    Had appointments I put into database show up in calendar but when I go back to contacts they disappear and yes, no longer does the calendar sync with my google calendar.

    Oh, did I mention the add on for gmail no longer shows its button. Very frustrated and only solution is to buy upgrade. Not sure I want to. I have used act since its very early days.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s