Portal scrolling has always been a bit of a struggle in FileMaker Go up until the release of version 12. This article outlines some of the changes to portal scrolling in FileMaker Go 12 and we give a couple of examples how it can be set-up to give a very nice native-application look and feel. We also cover field scrolling.

Digital Fusion have been working out of Australia for a few years now, sharing an office in Sydney with one of our favourite clients - Streamtime. During this time we?ve had good success but not good enough for our liking.

As our human race progresses through the ages, we?re constantly after a bigger bang for our buck. We want more for less: more productivity for less effort i.e. efficiency.

FileMaker 12 is here, and with it comes many new cool new features, a lot of which are a result of the new css-based layout engine. In this article we are focusing on one small change borne out of the new layout engine which has massive potential for building new interface controls?

FileMaker Go has been "brought into feature parity with FileMaker Pro". In this article we'll look at what that means more specifically.

When our clients choose FileMaker it?s usually because they want to do things their way. They want a solution tailored to the way they do business ? they want flexibility and control. This is great and we love these forward-thinking visionaries.

We're rapt to see the new version of FileMaker released, a major release covering all 3 aspects of the FileMaker suite (FileMaker Pro, Server and Go) in one hit, and bringing a raft of new features along with speed and robustness improvements... all very good stuff, so here's a few highlights and what they'll mean for you.

This is the third article in our series of tips and hints for FileMaker. This time we are focusing on scripts - from their creation, to editing and debugging. Take it as it is - this is just an assortment of our favorite time-savers, shortcuts, tips, hints, tricks, tools of the trade and more…

Script triggers are a great feature in FileMaker that allow you to initiate a script when certain actions occur such as committing a record or leaving a layout. Not only do they run when user initiated, they can also be script initiated by script steps. This can sometimes produce unexpected results and so you may wish for triggers to be disabled. This article presents a very simple and elegant method of suppressing script triggers from firing when initiated by other scripts…