eshoshin

Got it all working now. Took about 4 minutes for the initial sync... probably because I had remnant junk in there from bailing out on the prior sync. Added a new record on mobile and did it again, only took 30 seconds. Thanks for all your help Tim. Ethan

Okay. The 4k records on the server don't have anything in either of those fields. Does that make a difference?

Do I set those fields on the server database or the mobile database? Or both? The server db has 4k+ records in the EasySync table. Mobile database only has one. This is after trying to sync last night.

So everything was working fine. I made a bunch of changes to the hosted file (layouts, etc. but no schema changes). Pulled down a fresh copy and followed your instructions for setting up the mobile database. Basically wanted a preloaded file for mobile. The sync hangs at "pushing payload to server." I let it sit for over an hour and it never changed. I can access the server just fine, so it's not the connection. Stumped on this. I went over the mobile database setup twice and everything is as it should be. Any idea what could be going on? Is it normal for the first sync to take hours? I don't recall it taking this long before. We're talking hundreds of records, not thousands (granted there were roughly 100 records when syncing before, but it only took a minute at most). I read you setup FAQ's about preloading data. Not sure what you mean by going to the Payloads table and updating the UTC Time field... there aren't any records in that table (not even in the old mobile file that was syncing fine before). Again, any insight is much appreciated. Thanks, Ethan

After my first sync, I now have duplicate records in all synced tables. Question: in the setup guidelines, it says to update all records so there is data in the ES_Record_UUID field using Get(UUID). It also says to do this on the mobile database setup... should the mobile database have different UUID's in this field than the hosted database? Seems to me that these should line up so the sync knows which record to work with, otherwise it's going to think the record was newly added and create a new one (hence all the dupes). I'm wondering if it would have been better to setup the hosted database first, then pull down a copy for offline and set that one up following the mobile guidelines. That would mean all the ES_Record_UUID's would match from hosted to mobile in their respective tables. Would that be the right approach? The documentation was not clear and almost suggested not to do this by it's wording (which was just "repeat steps 1-4 for from the 'configuring the hosted database'). Any insight would be much appreciated. Thanks, Ethan This is on FMS 13, FMA 13 and FMGo for 13. Mavericks iOS 7.1.2 on iPad Air

Wouldn't it make more sense to check to see if that window already exists, and if it does, bring it to the front rather than open a second window of the same thing? Unless there's a reason why someone would want two of those open. You could do this with Select Window[Name] and Error Capture. Set the error as a variable and then If [ get(LastError)] = 0 the window is already present.

"I am wondering, though, how filemaker itself differentiates windows with the same name? There must be some sort of unique window id somewhere." If a window "Contacts" is open already, then you open another window with the same name, FM will add a number identifier to the new window (i.e. "Contacts - 2"). I don't believe it's possible to have windows with exactly the same name open at the same time.