Designing Smart Apps Geared to Work for You
We develop custom solutions using the Claris FileMaker, OutSystems and Laravel Platforms
We're fully equipped to take care of your database hosting, backup and data security needs
Let us recommend the best platform and integrations to fit your needs and advance your business
We want to share our knowledge and love for software development with the world!
We have a Meetup group and YouTube channel dedicated to sharing our knowledge with the community
Download our popular FileMaker modules
We can help you integrate with other apps, streamline your work processes, identify your hosting needs, implement security best practices and more. You need a custom solution when you're tired of trying to fit your business model around your software, you're spending more time handling your data than your product, you crave efficiency and accuracy, your long-term goals seem unattainable in your current setup, you need to be in two (or more) places at once,
you're concerned about security, or when you need personalized reports, not one-size-fits-most reports.
This article will show examples of good comments vs. bad comments, and how you can improve your code readability by following a few key principles. In our previous blog posts on code readability, we showed how to enhance code readability by using spacing and meaningful naming without adding comments.
Some of you might be wondering, what’s wrong with comments?
Accurate, well-placed, informative, and intention-revealing comments are good; however, most comments are not this way.
I do code reviews for our developers. When I point out some of their scripts’ poor readability, nine out of ten times, they will react by promising to add some comments to their scripts.
But do you really need to use comments to enhance readability? Sometimes a few empty rows will do a great job.
Of all the FileMaker features introduced in the past five years, many feel that being able to specify cURL options for the Insert from URL script step is the most impactful. Why might that be?
With this feature, all third-party web services with APIs can be extensions of our FileMaker solutions, which expands what our FileMaker solutions can do. Developers can confidently take on web integration requests, and deliver them across the entire product line, including WebDirect and FileMaker Go.
Integration projects usually start with authentication. This article will explain how to approach basic authentication for a web integration.
This article explains the technique known as a single-pass loop, and why it is part of my script template. If you do a lot of error trapping or exception handling, this is a great technique to master.
Beginning in FileMaker 16, many developers have used JSON functions to pass script parameters and script results, which can be a very convenient way to pass multiple parameters at once. However, it can be tedious to write many Set Variable script steps just to parse out values from the script parameter.