GoZync 3.0: new for FileMaker 12

    Simpler Integration, More Scriptable, and now a Free Version.

GoZync is a framework for building offline FileMaker Go solutions that talk to hosted FMP files. With GoZync you can...

• Push and pull data over shaky (even 3G) connections.

• Gracefully handle disconnects in the middle of data transfers.

• Deploy new builds of the mobile files to your users.

• Pull found sets (just my data) down to mobile users.

• Rely on database transactions for reliable sync.

    Purchase GoZync

Purchasing options are found further down the page here.

    See GoZync in Action

Here is a quick video showing how you can work offline and then push edited records back up to your hosted FileMaker files.

GoZync system is perfect for Stat Bio-Medical and can’t say enough good things about how this is going to change my company and supporting my customers over night! Once again, thank you for saving my company and being able to let us Go Green.... Go Paperless with GoZync.... over night!!!

Bill Peloquin (more)             

Go Local

    Local FileMaker Go files run faster and feel more like iPad apps.

GoZync lets you deploy local files to your users: files that run ON the iPad or iPhone instead of from FileMaker Server. Local files run faster (and open faster) than hosted files, making them feel more like your users expect iOS apps to behave.

With GoZync you can deploy several smaller, single-purpose apps rather than asking your users to run the mothership system on their mobile devices. For more on the benefits of going local, and why we love this aspect of GoZync, check out Todd’s blog post "why go local".

Wow, you and your team are amazing. Thank you for the rapid response and assistance on these files. Thanks to your efforts, the team down in Haiti was able to go out, do patient visits, and successfully sync their patient data.

Joel Fauntleroy (more)             

Deliver New Versions

    Easily deliver new builds (new databases and/or new data) to your users.

Your users can simply click "update" to download the latest version of your mobile file. And unlike files delivered by email or via iTunes, new files delivered by GoZync clobber existing files of the same name, so your users always know which file is current.

Users can get new files while out of the office, over the same shaky 3G or WIFI connections.

You can decide if files come down empty, or with data (such as price lists or catalogs). And of course our scripts prevent users from updating their local copy while it had new records that haven’t yet been sent to your main solution (though you can change that behaviour if you need to since all that scripting in the mobile file is unlocked).

    Or use GoZync as a mini app store

In addition to this in-app updating, you can deploy GoZync as a file delivery portal--like a mini apps store--so your users can get copies of new apps you distribute. Here’s a short video.

Make New Records, or Edit Existing Ones

    GoZync can tell if a record exists, and then edit it.

It’s your decision if you’re just making new records on the iPad or editing records you bring down from FileMaker Pro.

When GoZync sends records back up to the server, the records are placed in an intermediate file. GoZync then "exlodes" the record into variables that GoZync scripts use to add or edit records. Because this data is presented in variables-- and moved into your records using simple SetField() commands, you can easily modify how GoZync works, editing records in only some cases, sending email notifications, running your own scripts, etc.

    New: Field-Level Merge

With this turned on, GoZync will only send the fields that have been changed since the last zync, instead of sending the whole record.

This can be a huge help if both the mobile user and hosted users may be editing the same record: if you edit someone’s phone number, and I edit their name, field-level merge lets both those edits get to the same record.

Or imagine that you have a collection of photos about a building the iPad. Without field-level merge, editing the caption of one photo would cause all the photos on that record to be sent up to the server: with field-level we only send the caption.