05-26-2009 01:43 PM
05-27-2009 05:51 AM
Follow the KB article below. This will require you to run the dbfixer on the server, create a new remote database, restore the remote, and run the dbfixer on the new remote.
08-04-2009 06:59 AM
The KB article referenced in my previous post also applies to ACT! 2009. Applying 11.1 update will also address this issue.
NOTE: The attached DBFixer must be run on all current remote and parent databases. Newly created remote databases will still have the initial issue of not syncing the affected data types, so the DBFixer must be run on new remote databases as well. Using the DBFixer will not restore the data that didn't originally sync, so if data is currently missing, create a new remote database and then apply the DBFixer.