02-20-2012 11:38 PM
We are sales agents and represent two principals. We have a single ACT! database that we use for customer management of both principals. A custom field allows us to determine which principal a customer is related to. In rare instances a customer may be related to both principals. None of this is sync'd and it all works flawlessly.
One of our principals has decided to implement ACT! and want to sync with our database. While we have no in principal problem with this it does introduce a number of technical issues. In particular, we only want data related to that principal to be sync'd. As I understand it we can configure the dataset to sync only a subset of the contacts, however, this can only be done on the master database not on the remote database. Thats the wrong way around for us. We have considered using a unique database for each principal but that introduces issues with the calendar (you can't have a single calendar with all your events).
Any thoughts on a workaround?