Introducing Modular FileMaker

Several of my closest collaborators and I have been working for many years on coming up with a methodology for building highly re-usable FileMaker code. This has become easier in recent versions. There is still a long way to go.  But I think we have finally reached a state where we can begin to get some real benefit from adopting this style.

And thats just what Modular FileMaker is. It’s a style. It tries to be light and unobtrusive. It is NOT a large monolithic framework, or a comprehensive naming standard. It focuses only on the areas that impact sharing and modularity.  I will have lots more to say about this in the coming days, but for now you can read more on the About page.

This is a work in progress. The Spec is not done yet. But it is time to take it public 🙂

5 responses to “Introducing Modular FileMaker”

  1. john renfrew says:

    thanks for this start Todd. great session at Pause and really keen to see how this develops.

  2. Tom R. says:

    I’m really excited to use some of the modules here. This is a great project I think.

    One thing I noticed is that each of the modules has a “Public” and “Private” folder in Manage Scripts. When copying multiple modules into a single .fmp12 file, these folders are renamed Public 1, Public 2, etc. It would be helpful if these folder names included the module names, e.g. “BrowserNav – Public” or something similar.

    Best regards,


    • Todd Geist says:

      Hi Tom,

      Yeah this is a good idea for a number of reasons. I have started to do this with some of my internal modules. I have been using an abbreviation of the module name, but maybe it is better to use the full name, not sure yet. I think something like this will make it into the specification at some point.


  3. Paul Jansen says:


    Is there any way of finding out how many times a module has been downloaded?

Leave a Reply

Your email address will not be published. Required fields are marked *