1 Reply Latest reply on Oct 26, 2016 8:33 AM by philmodjunk

    Should flag fields be globals?


      I am creating a solution that will work locally on an iPad.  My question is, I want to be able to set various “flag” fields in the file before I distribute it, and am wondering whether or not these flags should be globals or not.


      For example, when I send out a new version, my plan is to set a flag in a file preferences table to “1”, as in


      preferences:is_update = 1


      When my startup script sees the flag is true, it runs an import script that imports the data from the old version located on the iPad in the FM Go file area.  Once the script is finished, it will set


      preferences:is_update = “”


      Does it matter whether or not the flag field is a global?


        • 1. Re: Should flag fields be globals?

          If it is defined in a file local on the iPad and not in a hosted solution on a server, it makes very little difference whether you use a single record in a table with non-global fields or you use global fields.


          Global can be more convenient to access in scripts, etc as you can access them from any window and layout in your solution.