FILEMAKER LAYOUT DESIGN CODE

FILEMAKER LAYOUT DESIGN CODE

Looking at the code behind the function, I realized that it used the new ExecuteSQL function introduced in FileMaker 12 (which IвЂ™ve written about in a previous blog post). I did some digging, and found a custom function at that would do exactly what I wanted ( click here to view the custom function) вЂ“ by submitting a table name, I could get a list of field names for that table. I could have worked around it by keeping a hidden layout that just contains all the fields for each table ( I usually have something like this anyway since I find them useful for scripting purposes), but IвЂ™d have to worry about it not being up to date if I added some fields to the table, but forgot to add them to the layout. Unfortunately, the design functions didnвЂ™t solve the problem that I had вЂ“ there is a Design function called FieldNames, but it lists the fields that are on a layout, not for a table. They arenвЂ™t something that youвЂ™ll use everyday, but there are some creative uses for them IвЂ™ve used the ValueListItems in quite a few calculations to get (for example) a unique list of values from a field. RelationInfo вЂ“ a list of all relationships for a given table.ValueListItems вЂ“ the values in a given value list.ValueListNames вЂ“ the name of the value lists in a file.ScriptNames вЂ“ the name of the scripts in a file.LayoutNames вЂ“ the name of layouts in a given file.If you havenвЂ™t had a look at these, IвЂ™d suggest taking some time to have a quick look at them they can give you some interesting information about the structure of your database including: The first place I looked was the Design functions. Recently, I wanted to pull a list of field names from a table to display to the user.

Filemaker layout design