2 Replies Latest reply on Sep 9, 2014 4:23 AM by keywords

    Find Based on Unassociated Layout

    rsmellette

      Could anyone else use a whole section on translating procedures from Access to Filemaker?

       

      In Access I found it convenient to make an unassociated (not the right word) form - aka, a layout not connected to a table, aka a dialogue box - so users could create their own complex queries in a simple way. Drop Down Combo Boxes allowed them to pick what they were looking for and go.

       

      Can I do this in Filemaker?

       

      I need to:

       

      1) Create a Combination Value List based on an ID Field and a Text Field with only the Text visible (Text may not be unique, so I need the ID)

       

      2) Create a Layout or Dialogue Box with:

      a) A Drop Down Box tied to the Value List (This is a temporary Field, I won't keep the choice)

      b) A button that opens a layout based on the user's choice in "a" above.

       

      I could do this in Access in my sleep. I hope someone here can show me how in FMP without losing any sleep.

       

      Thanks,

       

      Signed... frustrated.

        • 1. Re: Find Based on Unassociated Layout
          jbrown

          Morning.

          A couple of things:

          1. Every layout has to have a table associated with it. In this case, a query layout, the table that underliesthe layout could be a resource table. Many develoeprs create a table of nothing but global fields in which to use throughout their system. This would contain just one record. So it is possible to create a query layout based on this table and potentially use global fields to enter values to search against data tables.

           

          2. Your value list has to come from a table and two of the fields in that table. When creating a value list, you have the option of typing in your own values or selecting fields from a table. If you do the latter, then you can do exactly what you require: Show only the text, but store the ID in the field. This is a common practice. (There's a refinement to this that is possible, and  can be explained separately)

           

          3. Again, your layout, based on the Resources table, can contain a global field called Layout which contains the value list of values from the table. I assume you'd have a table of layout names which correspond to the layouts in your solution. The user could select a layout from the list and a button could be programmed to go "Go To Layout By Name". In the calculation box of this choice you simply enter the global field. This will go to the layout with the name of the value in this field.

           

          You have to make sure, of course, that the layout names in the table are exactly the same as the ones you want the user to have access to while using this method.

           

          Here's a sample file.

           

          One note, if you're trying to create a value list that contains the ID and the layout name, as you describe in your post) then "Go to layout by name" won't work because the value of the global field is the ID not the name. We'd have to further refine it.

          • 2. Re: Find Based on Unassociated Layout
            keywords

            What Jeremy describes is pretty much what I would suggest:

             

            1.     Create a bunch of global fields in which users enter the varius find criteria they want

            2.     Create a script which (1) collects the find criteria as variables, (2) goes to a suitable layout to actually perform the Find/s, and (3) ends on a suitable layout which displays the found record/s for the user's pleasure.