In this edition of the spotlight, we’re taking a deep look at the Calendar. Prior to FileMaker 19.1, building a robust, native calendar interface in FileMaker typically required some form of repeating fields, portals, and/or list view, combined with multiple layered objects or layouts. With the Calendar Add-on, a calendar interface can be quickly added to any solution with very little hassle.
With the recent highly publicized attacks on Colonial Pipeline and JBS, we’ve had questions from some of our clients about protecting FileMaker data from ransomware attacks. While we are always careful to make it clear that we are not security professionals, we also try to do our best to answer our client’s questions, and so we have done some self-education recently as well as group discussions during our weekly developer meetings.
One of our large clients recently had a change of ownership. The new ownership team brought in a security analysis firm, BlueOrange, to perform a security analysis and penetration testing study of our client’s IT infrastructure, including the custom Claris FileMaker solution we developed for them and have been enhancing and supporting for about ten years now. We haven’t had the chance to work with a firm like BlueOrange in the past on an enterprise scale security analysis. It was a good experience for us, and I thought a report on this process would be interesting to the larger Claris FileMaker community.
There is a category of disagreement on the earth I like to call “Bar Fight Topics”. These are the things that can turn perfectly happy friends and business partners against each other, with the help of a third wheel often known as Jack Daniels.
The latest release of FileMaker Pro, 19.2.2, includes a few new developer tools as well as a revised quick-start experience. The quick-start experience is still in preview on MacOS only, but I had a chance to give it a whirl and I found some interesting use cases.
We recently had an opportunity to make a solid, real-life comparison of Top Call Statistics enabled versus disabled in a user-heavy, multi-office solution. We’ll describe our scenario and observations in the remainder of this article.
