2 Replies Latest reply on Jul 12, 2012 3:29 PM by philmodjunk

    Scriptstep Go To Next Field enters locked fields

    kalle_samuelsson

      Summary

      Scriptstep Go To Next Field enters locked fields

      Version

      12.0.1

      Operating system version

      MacOSX

      Description of the issue

      The scriptstep "Go To Next Field" sets focus to fields on a layout even if they are set to not be entered in browsemode. This is true only if the scriptstep is performed inside a script, not if performed directly from a button.

      Steps to reproduce the problem

      1: Create a layout with three fields visible, f1, f2 and f3.

      2: In layoutmode, uncheck "Field Entry" in "Browsemode" for field f2 so that the user is unable to set focus to that field while in browsemode, leave f1 and f3 as they are.

      3: Create a new script and move one instance of the scriptstep "Go To Next Field" to the script

      4: Save the script and enter browsemode, also make sure to have atleast one record in your foundset

      5: Run the script a few times by selecting it from the Scripts-menu

      Expected result

      That the "locked" field, f2, should not be given focus by the script. Focus should switch between f1 and f3.

      Actual result

      Field f2 is given focus by the script, just as f1 and f3

      Exact text of any error message(s) that appear

      No error

      Configuration information

      It is actually the same in FileMaker 11, but it can´t be behavior as expected? Why does the scriptstep behave differently when bound directly to a button?

      Workaround

      Simply do not use it =)