5 Replies Latest reply on Apr 29, 2017 9:05 PM by itsrayland

    Field-level locking


      FileMaker doesn't seem to offer much in flexibility when it comes to field level locking. No calculation engine I can find. All I have is

      1) Modifiable

      2) View Only

      3) No Access


      I have a layout that contains 2 container fields. I'd like to lock those container fields for edits after the container has been filled with a pdf. Does anyone know how to do this with Manage Security? or some other means?



        • 1. Re: Field-level locking

          If you were to move those two container fields into a separate table linked in a relationship to the original table, you can then set up record level locking on the record. This does not necessarily require a major redesign of your layout, just a case of repointing the container fields to the new table.


          Otherwise you are looking at using scripts and layout design options to try to control access which can be problematic. You can use one layout that permits access and another that does not and switch layouts. Or you might stack two copies of the same field object, one that permits access and one that does not and use Hide Object When to control which copy of the field is visible on a given record.

          1 of 1 people found this helpful
          • 2. Re: Field-level locking

            use two container fields one on top of he other.. set one to be accessible in browse mode in inspector and the other not acessible. hide the one that is enabled for entry in browse mode with the hide object when calculation in the inspectpor

            • 3. Re: Field-level locking

              I really like this idea and am embarrassed that I didn't think of it myself. Prior to reading this, I saw that there's a way to simulate locking of a field by using an extra binary type field "is_locked" , then setting it to 1 when a pdf is dropped into the container. For the locking simulation you can utilize a validation calculation. It's a little weird, but it works.

              However, I really like the idea of dropping those containers into their own table, that way I can easily use Manage>Security and the privilege sets to control when it's locked.



              Thank you!!

              • 4. Re: Field-level locking

                The main general issue with validation calculations is that they allow the user to transgress the validation rule and then toss up an error message. I prefer to steer them away from making the error in the first place--leaving validation rules in place as "insurance" just in case my interface design has a "loophole" that I didn't allow for.

                • 5. Re: Field-level locking

                  Hi jdev!


                  Here's a potential option!

                  1. Create the same container twice.
                  2. The rearward container will have browse tick box OFF
                  3. The forward container will have browse tick box ON
                  4. The forward container should be set to Hide when the Container field calculation is > "0"


                  In this way the the same field is displayed twice, but once its occupied by a file the "browsable" container will be hidden revealing the "unbrowsable" container field.

                  Hope this helps! Let me know if it makes sense!




                  ///  RAY LAND  ///  @ITSRAYLAND  /// C 386.362.9312 ///  O 866.352.7295