Category Blog

A new bug with FileMaker 18’s Send Mail script step has come up recently. This bug only occurs when sending email via SMTP server. It also only happens when using Gmail’s SMTP service. The bug is apparent when users attempting to Send Mail via SMTP encounter this pop-up:

Read More

Our favorite time in Portland is here! The Rose Festival, Pride Week, Fleet Week, Portland Craft Beer Festival, The Blues Festival and Bridge Pedal are just a few of our favorites, but with each of them comes traffic on both land and water. While lots of apps can help with traffic navigation, most can’t account for bridge lifts, leaving users with no idea how long they’ll be stuck in traffic. (Remember, turning off your engine reduces pollution and helps keep our city beautiful!)

Read More

FileMaker Server added a new feature to its existing tools to ensure the integrity of its hosted databases. After checking files at startup, and before opening any database, if inconsistencies are found due to abnormal closing of files (i.e. power failure or crash), FileMaker Server now uses the restoration log feature to restore files to their last consistent state.

Read More

Today we offer a new minor update to our ever-popular fmMapping Module. If you’re not familiar with it, this is a simple-to-deploy, FileMaker-native module for integrating Google maps with your FileMaker application. It has the ability to map multiple address records on a single Google map, using a webviewer.

The updates today fix a minor bug, provide better documentation of recent changes to Google’s API, and more importantly, remove the need for custom functions. The older version relied on two of them, and they’ve both been replaced with FileMaker 16’s native JSON functions. If you’re running a version of FileMaker earlier than 16, this update is not for you.

You can download the new version HERE, and let us know if you need help deploying it, or if you’re interested in added features.

Note: If you’ve had trouble recently with Google maps being drawn with a darkened background and the words “For development purposes only”, it’s due to changes made by Google:

1. The Google Maps API now requires all requests to be submitted with an API key. Formerly, they allowed a certain number of requests without the need for a key.
2. For the fmMapping module to work correctly, there are two separate APIs that need to be enabled in the Google Maps Developer Console:
   • Geocoding API
   • Maps Javascript API

fmMapping is one of our best-loved modules, and has many cool applications for use. We’d love to know how you are integrating this module into your solutions in the comments section, so let us know below!