Software Venture Consulting

FileMaker Pro downloads & Resources
FileMaker Custom Functions
FileMaker Web Viewer Examples
FileMaker Pro & Lasso Consulting
FileMaker Books
FileMaker Articles
FileMaker Error Reference

Free Web Tools
Free FileMaker Tools

Personal Pages

Shopping Cart
Shopping Cart


Free Newsletter


Privacy Policy

FileMaker is a registered trademark of FileMaker, Inc. in the U.S. and other countries.


 FileMaker Pro Custom Functions

List  |  Show Random  |  Upload  |  Add This to Your Site

CorrectContext ( getFieldName_ )

Rate this function:  

  Average rating: 4.3  (31 votes)
  Discuss this Custom Function

Malcolm Fitzgerald, FM Studio

CorrectContext is used to determine whether the current layout table name is the same as that of the field being tested

Sample Input:
CorrectContext ( getFieldName ( table::field ) )
Sample Output:

 Then copy & paste into FileMaker Advanced's Edit Custom Function window.

Click here to copy To Clip Manager if you have myFMbutler's Clip Manager installed


This function provides a simple means to determine whether to proceed with script actions. Many script steps perform actions which depend on the current context. In the wrong context the script will fail, at least, and could do damage by adding, editing or deleting records. The Go To Related Record is particularly susceptible to failure and usually needs error trapping.

Dangerous Code:

Go to Related Record [ "children"; "formview" ]
Delete All Records [ no dialog ]

Problem: if there are no related records the GTRR script step does not go to the "formview" table and find no records. It stays where it is, in the parent table. The Delete All Records script step will then delete all Parent records in the found set.

Safer Code:

Go to Related Record [ "children"; "formview" ]
if ( CorrectContext ( getFieldName( children::id ) ) )
Delete All Records [ no dialog ]
end if

The CorrectContext function will accept any string and compare it to the current layout table name. However, hardcoding table names and field names is never safe. The safest and the most reliable way to use this function is to use the built-in function GetFieldName() to pass the name of the key field. GetFieldName uses a reference to the field, if the field name changes or the table name changes, the field reference is updated automatically. Nothing breaks, all your code continues to work.

Note: these functions are not guaranteed or supported by Please contact the individual developer with any questions or problems.

This is my Custom Function and I want to edit it


There are no comments yet. Be the first to post a comment about this Custom Function! Please try to keep it brief & to the point. Anyone can post:

Your Name:
characters left. If you paste in more than 1500 characters, it will be truncated. Discuss the function - advertisements and other useless posts will be deleted.
Answer 6 + 3 =
Search for Custom Functions:

Custom Functions Widget
Download the Custom Function Dashboard Widget for OS X
Keep all the latest Custom Functions right at your fingertips!

Newest Custom Functions:

1. ExcludeValues(MyList ; Out)
  (Wed, Mar 21, 7:23am)
2. PreviousMonthEndDate ( myDate )
  (Wed, Mar 07, 3:35am)
3. PreviousMonthName (myDate)
  (Wed, Mar 07, 3:33am)
4. FmTableFields ( tableName ; fieldsInclude ; fieldsExclude ; classExclude ; typeExclude ; prefixExclude )
  (Fri, Mar 02, 6:32am)
5. sql.getTable ( fullyQualifiedFieldObject )
  (Thu, Feb 22, 8:36am)
6. sql.getField ( fullyQualifiedFieldObject )
  (Thu, Feb 22, 8:34am)
7. FilterOut ( ListA ; ListB )
  (Wed, Feb 21, 6:11pm)
8. Char0 ( )
  (Sun, Feb 18, 2:35am)

RSS Feed of Custom Functions