Reducing Field Counts
Unlike other programming languages, where the database is often separate from the language used to code solution logic, FileMaker includes everything, all wrapped up into one potentially giant mess of spaghetti.
In order to avoid the often inevitable pitfalls of being overly complex, you must code your FileMaker solution with efficiency and simplification in mind. FileMaker has many places where logic can exist in. It can be on an object, in a parameter, within a script, within conditional formatting, in an auto-enter setting, and obviously within the graph and data structure.
Your primary goal of keeping things simple means you need to be aware of how a FileMaker solution can grow and your field count is one of those areas. If you can reduce the number of fields, then your solution will be easier to understand. Choosing from three items is always faster and easier than choosing from fifty. With good segmentation, clean organization and a focus on limiting the number of "things to manage", you can create a very powerful FileMaker solution which doesn't suffer from object overwhelm. That's what this video is all about.