Sync is not as simple as you might think.
i have sucessfully used GoZync from SeedCode to sync data between iPhone and hosted FM.
Others have had success with MirrorSync by 360works or rolling there own.
EasySync is a free product that will require some work to get right as it is not supported freeware
No, sync is definitely not simple. I've built sync interfaces before. Was merely saying that the particular situation I'm looking at in this case is relatively simple, as far as sync goes.
Thanks for your feedback on the GoZync. I've read all the FM literature but eager to hear from actual use cases. Appreciate the response!
If you are only dealing with full records and the clients are essentially Read Only at the field level it does get simpler.
Deletes are super easy to manage. I would run PSOS to match up primary keys and return a list of keys to delete.
New records and updates can be handled with Import Records right? Import is usually pretty fast.
How many total records? If there are 300k records and you are only needing to transfer 6k you might do it another way.
So...a little update. I have spent the last few days working with Goya's RESTfmSync and it is a very good fit for what I'm doing. It is also easy to dig in and figure out what's going on and customize if need be. I've added a few things to it and in testing sync in the field, I'm getting great results. The biggest downside I've found is that when pulling recs from the server, the recs that are pulled are the ones modified since the last successful Sync to the client of ALL tables you are syncing, i.e. the last time the client ran a successful sync session. So, if you have 100 recs and a sync to client fails halfway through, you'll pull all 100 recs again on your next attempt instead of skipping the 50 you already have. Actually, I believe RESTfmSync has a way to ignore pulling certain recs. I need to look into that as it probably can be used to fix this issue.
Thanks for the responses.