i tried syncing (using ac's sync prog) between two different offices this week (which have both had many new and different pts in the db), and it gave me a kinda frankesteined collective db where say, demographic info for pt A would be put w/ imported items for a pt B--in short, it was a mess.
i think sync might work if you didn't add new pts to the 'satellite db' (and hence, avoid having diff pts having the same pt ID-b/c i think that's the one being used as the primary key), or maybe there's a way to redefine the primary key (like last name, first name, dob combined into one string), so that you don't have 2 pts w/ same key.
