Using Gateway Files

One of the greatest joys of working in technology is that you never really have to stop learning - although you certainly can. Everything also moves so fast that it often feels like you can’t keep up. The great thing about FileMaker is that you're not stuck in the '80s or '90s when the software first started - you get to explore as widely as you like. FileMaker can literally reach into almost all aspects of technology.

You can learn about relational structure, SQL, REST, web APIs, and whatever the next challenge is to make your data work the way you want to work. In this week's video, I focus on a topic related to solution architecture. It's presented in the form of using a Gateway file. This is a term I use to simply indicate that a FileMaker file acts as a technical arbitrator - helping decide which direction to take and what can be done before entering your “true” solution.

Yes, the Gateway file is part and parcel of your overall solution, but as a component that can be easily separated, it can provide critical functionality that makes development and maintenance a bit easier. If you're currently using a single-file FileMaker solution and have reached a point where your technical debt feels overwhelming, moving to this type of file setup may offer a breath of fresh air - whether you're revamping an older solution or starting something new.

Click the title or link to this article to view the video.

View the full article