3 Replies Latest reply on Jun 2, 2009 7:17 AM by mrvodka

    Navigational Layout

    swhite

      Title

      Navigational Layout

      Post

      I'm trying to create a navigational layout where users will select a project and then the detailed project record layout will be shown. I would like for the initial project selection to remain for the user's session, unless they go back to the navigation layout and make a new selection.

       

      I tried creating a new layout, then creating a global field for "g_project_list". I placed the global field on the layout, made a value list from the "project_id" field, and associated my value list to the global field's drop-down menu. I then wrote a script to go to the detailed project layout and go to the specific record specified by the g_project_list selection. Everything seemed in order, as the drop-down menu correctly listed the projects. However, when I select an item in the list I get the error:

       

      "This action cannot be performed because this field is not modifiable."

       

      I guess global fields cannot be used this way...do I need a global variable? If so, how does one allow the variable to be controlled interactively by users?

       

      I also thought of using a portal, but I'm already using the projects table in the layout and it seems you cannot use a portal to a table on a layout using that same table.

       

      Thanks,

      Scott

        • 1. Re: Navigational Layout
          philmodjunk
            

           

          The confusing part of "This action cannot be performed because this field is not modifiable." is that Filemaker doesn't tell you which field is "this" field. You should be able to use a global field in the manner you describe. Given the error message you describe, it's possible that there is step in your script that is triggering it.

           

          Generally, you get this message if you attempt to modify the contents of a calculation field or a field that has been set to prevent user modification in its field options.

           

          Check your field definitions and examine your script carefully. If you are using fmp advanced, you may want to use the script debugger to step through your script.

          • 2. Re: Navigational Layout
            swhite
              

            Ok, I changed the field to not execute a script at all to see if I could get the selection to work, and I get the same error. Per your suggestion I looked at all the field definitions, and it struck me a bit odd that you sited a calculation field as a potential cause, since I could choose only a calculation or a summary for the field type. Something I should have mentioned is that this table is actually an ODBC connection to an Oracle table. I was adding the global field to this table, which FileMaker allows, but these fields are limited to just calculation and summary field types for non-native Filemaker tables. So, I created a new, regular FileMaker table and added my global field there. Then, I was able to choose text as the field type. I rigged everything back up... the error is gone and everything works. So, it was a calculation field problem.

             

            Thanks Phil!

            • 3. Re: Navigational Layout
              mrvodka
                

              "Something I should have mentioned is that this table is actually an ODBC connection to an Oracle table"

               

               

              This was a pretty big oversight...