7 Replies Latest reply on May 10, 2016 5:56 AM by ajs@ml1.net

    deployment to ipad

    ajs@ml1.net

      we are new to the filemaker platform, and have developed an app on the PC but want to deploy to the ipads in the organisation using filemaker go.  We have created a script on the app to 'save a copy' so that when we open the file from the host we can then save a copy to the ipad for ingle user use offline.  The command doesnt seem to work on the ipad from the button.  Can anyone advise please?

       

      thanks

       

      Andrew - Derbyshire, UK

        • 1. Re: deployment to ipad
          Mike_Mitchell

          Save a Copy isn't supported for hosted databases. If you want to have an offline version of the database, your best bet is to implement a mobile version and a syncing solution. There are commercial syncing tools available (GoZync from SeedCode, MirrorSync from 360Works, or EasySync - which is open source). You can also roll your own, if you're so inclined.

           

          Another option would be simply to copy the database from a backup down to the iPad, then import the records that have been changed back to the hosted solution manually. This is risky, since you can easily screw up the import, and you have to be careful about multi-user situations. If two people make offline changes to the same record, who wins? What if one user deletes a record, but the other needs it?

           

          As you might see, synchronizing multiple copies of a data system isn't a trivial exercise. You will need to think through your business rules and all the various scenarios and make sure you understand what can and will happen. Nevertheless, given that careful preparation, syncing solutions work quite well.

           

          HTH


          Mike

          • 2. Re: deployment to ipad
            ajs@ml1.net

            Hi Mike,

             

            thanks for the response.  The database on the ipad will be completely standalone and just issuing PDF's back to base via emails.  It was simply the best way to get the version onto the ipad that we were looking for.  However we have now linked a version to a googledocs page, and a link to that allows a download, followed by 'open in filemaker go', which seems a simple solution , after which it opens directly in filemaker go.

             

            thanks

             

            Andrew.

            • 3. Re: deployment to ipad
              Mike_Mitchell

              How are you getting the data into the GoogleDocs version?

              • 4. Re: deployment to ipad
                ajs@ml1.net

                We are copying the whole database into the googledocs page, just using it as storage.  Then linking to it via a web url for download.

                 

                 

                 

                 

                 

                 

                 

                regards,

                 

                cid:image001.jpg@01D06166.55433250

                 

                Andrew Steele

                • 5. Re: deployment to ipad
                  rgordon

                  Another option you could use is to store the file in a container field and use export field contents to bring the file to the iPad. This option would avoid the Open in option that you get with Google.

                  • 6. Re: deployment to ipad
                    Mike_Mitchell

                    Okay. Wanted to determine if there might be a risk of file corruption. What you want is for users to copy the file down, not try to open it on the remote drive. Otherwise, the original file can be damaged or others locked out when they try to access it.

                     

                    rgordon's idea of using a container field is actually quite good for this use case. It avoids the GoogleDocs issue entirely.

                    • 7. Re: deployment to ipad
                      ajs@ml1.net

                      Thanks guys – we will try the container method.

                       

                       

                       

                      regards,

                       

                      cid:image001.jpg@01D06166.55433250

                       

                      Andrew Steele