myIdea Logo

My Filemaker Pro Programming Standards: Custom Functions

This page is part of the internal FileMaker Pro programming standards of Lutz Pietschker. No claims of any sort can be derived from the description of these standards. In particular, no claim can be made that these standards are complete and without errors, and that any of my software projects follow to these standards in part or completely.
The page content was last revised on (ca. 2008)

Go to start page


Document Content

This document describes how to write and employ custom functions. It also describes some standard custom functions found in most databases.

Related documents: Naming Conventions for custom functions

Custom Function Conventions

Custom functions are used for the following purposes:

  1. To encapsulate plug-in functions
  2. To hold calculations that are used very often
  3. To encapsulate static values (constants)
  4. To provide flags that can be evaluated in a Database Design Report

Standard Custom Functions

Standard Calculations

Static Values (Constants)

Status Flag Constants

These constants are used to indicate the progress of database programming. They are used to flag pieces of script code and calculations that are not complete. The value of these functions is always =1; they follow a similar naming convention as the other constants, but the name starts with "lpTODO_", and the last part of the name can be freely chosen to indicate what remains to be done. The following status flag constants are examples:


This page is copyrighted by the author according to the copyright note.
All rights reserved. Lutz Pietschker, Berlin/Germany, 2011 ff.

, last change 2011-03-12