I’m sitting in the Hyatt, Orlando International Airport, just having finished a slice of key lime pie while I wait for my flight home from the annual FileMaker Developer’s conference, FileMaker DevCon to those of us that have been attending for years.
The process of updating FileMaker files in iOS has always been sort of a question mark, with multiple ideas for how to best accomplish it, each with their own limitations. At PBS, we developed a process to update files in iOS a number of years ago, but we’ve updated the process with some of the newer FileMaker 18 features that make the process more seamless, while altogether giving it a more native look and feel.
Portage Bay is looking to hire a new developer to join our team of FileMaker and 4th Dimension developers. We’re a group of experienced developers, some certified, some not, that work together on a variety of projects for clients in different industries, education, and government.
Relationships are the basis of relational database design. When set up properly, table relationships will ensure your database runs like a well oiled machine. However, sometimes we run into systems where relationship keys are open to the user, exposing data to the risk of human error if a relationship is changed improperly. It’s sometimes desirable to refactor these relationships to use a proper artificial key relationships to connect tables, a laborious task depending on the size of your database. This post discusses a convenient trick to populate Primary Keys, a reminder about mismatched data types, and a modular script to help populate foreign keys when refactoring a key relationship.
When developing FileMaker solutions, one of the issues that always comes up is the lack of Version control options. How can you use Version control with FileMaker, and what is it? Read this article to find out.