2 Replies Latest reply on Aug 29, 2013 12:42 PM by philmodjunk

    Migration from Bento for iPad/iphone to FileMaker and Filemaker Go issues

    RickLlewellyn

      Title

      Migration from Bento for iPad/iphone to FileMaker and Filemaker Go issues

      Post

           Are there and capablities or other limitations that were supported in Bento on the iphone/ipad that are not supported in the Filemaker Pro/Filemaker Go?

           Are Maps and location like Bento supported? Is it tied to the Google Maps App or can in use Apple Maps?

           Other isssues?

            

           Rick

        • 1. Re: Migration from Bento for iPad/iphone to FileMaker and Filemaker Go issues
          TSGal

               Rick Llewellyn:

               Thank you for your post.

               FileMaker Pro doesn't have a "Location" field per se, but you can extract the location using either the Location function (latitude and longitude) or LocationValues function (latitude, longitude, altitude, horizontal accuracy, vertical accuracy, age of value in minutes).  You can then use a WebViewer to display the location.

               Bento was able to sync the data between the Mac and your iOS device.  FileMaker does not have built-in syncing capability, but with FileMaker Go, you can connect to a file hosted on a Mac (or Windows) in real-time, so you don't have to wait to sync.

               FileMaker Pro does not have any field types that display as a table.  However, you can simulate a table by using either a Portal into another table or use a Repeating field.  If you used the Bento 4 to FileMaker Pro Migration Tool, the columns of your Simple List fields will transfer to repeating fields in FileMaker Pro.

               Let me know if you need additional clarification.

               TSGal
               FileMaker, Inc.

          • 2. Re: Migration from Bento for iPad/iphone to FileMaker and Filemaker Go issues
            philmodjunk
                 

                      FileMaker Pro does not have any field types that display as a table.

                 Hmmm, the results of an ExecuteSQL query would seem to produce that table all in one field result. wink

                 And please don't use repeating fields without being very careful to consider alternatives. THere are very, very few places where a repeating field is the best option--almost always a related table of records in one or more portals makes for the same interface but allows for much more flexibility in how you work with that data.