We have 2 computers that used to sync nicely back and forth. However, the last couple of days we have had problems syncing. Everytime we sync - all my personal activities and all tasks dissapear. I have restored the database from a back up and we have synced again a couple of times. Each time we sync now my activites and the tasks dissapear. Please help us know how to solve this. We have a current backup of the main database - but data entered on the 2nd computer is not transferred without loosing activities & tasks.
I would strongly suggest running a database Check and Repair on both computers, then running the sync, then running check & repair again. If your activities do not return, try running a full barrage of database maintenance by following these instructions: http://kb.sagesoftwareonline.com/app/answers/detail/a_id/19642
OK - tried all your suggestions. All the tests say repair or rebuild done successfully. When I try to log in again under the 'repaired database' now the first thing that comes up is the following error: Error: Invalid recur spec: Monthly named - day pattern with no modifier. I have no idea what this is or why it couldn't be repaired with the tests. I've tried almost all of them. I don't use reports so I didn't do those... Thank you for your help - any more ideas?? Act is vital for our business - so having it working again is critical.
It seems like you have at least one broken recurring activity. When I see this error it's because of an activity that is syncing between Google or Outlook. Are you currently syncing activities with either of these platforms?
Usually I would send these types of issues to our database managament team to have them repair the database.
We aren't syncing with either Google or Outlook. Just between a Mac (running a Windows platform) and Windows 7. How do I send it to the datatbase managment team to repair it?? and what will that cost??
They charge based off of the number of contacts, but they don't charge until they have the database fixed. It's a good way to tell if there is anything they can do in the first place. i would suggest sending it in, anyways. At the very least we can determine if it is a database issue or not.
