The attempt to push data to the server has failed. (The message received from the server was: "111A01C0-27AE-414B-AC1C-DC56C83F877E
So I am new to EasySync, and trying to get the best from it.
I am using it more to replicate a subset of a live database for external clients to access, but they will not be changing anything, so my only requirement is to pull data to my 'Mobile' dataset from my 'Hosted' dataset.
At the moment the live database is approx. 120k records, but this grows daily between 100 and 300 records for the main customer view, and possible 3 times that for associated activity.
I seem to have a serious speed issue, in that trying to sync the mobile version just locks everything up, trying to do an initial sync.
I can manually pull the data over at the end of a day, then mark all of these as EX_Exclude 1 and import them manually into my new portal
Set a OnCommit on the maincustomer view, so any changes will make the ES_Exclude to 0, thus marking these for sync
Question 1: How do I set these back to 1 once the sync is done?
Question 2: Is there a way to Schedule the sync to happen every 15 minutes so it has lessto sysnc, meaning less traffic?
Question 3: If I cannot schedule it, how do I prevent the 2 database's from appearing to lock, preventing users from working on either side, or slowing everything down?
Any help with this would be very appreciated as I am totally stumped at the moment.
By Joshua Willing Halpern
Otherwise if you're using EasySync and struggling with sync check, give my solution a try!
I've attached the new file below and linked to the old thread for continuity.
EDIT: For anyone interested in a demonstration of just the algorithms' performance difference before updating sync check, I've uploaded a raw concept file.
Have been using easySync for a while, but recently I have a problem where Close File ["Hosted_Database"] does exactly that on OS X but leaves the server open on iOS.
OS X: FM Pro 14 & 15
iOS: FMGo 14 & 15
Tired adding a Close File ["Hosted_Database"] in line 136 of "Sync With Server" at the beginning of #restore user interface
but this just generates an error 301: which is record is already in use. But of course the error only occurs on FMGo.
I must have done something simple to cause this but not sure what… any ideas are most welcome.
By Steve Cooper
I am conducting an initial test of FM easy sync. I am working on a system that I have in production with synchronization logic that I scripted myself (to iPads from FM Server). The sync to the iPads using my logic is rather ponderous, so I am researching alternates to speed things up.
I carefully applied the changes described in the FMEasySync setup document to my server file & the client file. I cleared all data from the client file - anticipating it would then do a full synchronization from the server to the client.
The primary table has over 150,000 records, so I did not expect it to be quick, but I am puzzled at what happened. It seemed to run without error, but was so slow, I thought it had stalled. I waited over 24 hours and in that time the progress indicator said it has processed about 500 records.
I conducted a brief review of where it was going in the debugger, but could not see any obvious problems with how I had inserted the elements into my solution.
I figure, there must be something grossly wrong with how I put this together. Any thoughts out there?