Setting up a FileMaker server and never looking at it again is a recipe for disaster. Are your backups running? Has the scripting engine crashed? Are you running out of memory or CPU? Are your integrations taxing your solution? If any of these things happen, or if you're not monitoring to ensure they don't, you're putting your data at risk.
While the big announcements from this year's DevCon set the tone for an exciting and revelatory conference, the week held even more in store for us.
Every year, we journey to a different locale for the annual FileMaker developer & user conference, DevCon. Each year is jam-packed with informative sessions, groundbreaking innovations, engaged partners and a gaggle of developers eager to share with and learn from each other. This year's conference in Orlando was no different... except it was.
When FileMaker 16 was released in May 2017, there was plenty of fanfare surrounding the many new features it introduced. WebDirect, however, did not get much attention or focus on any changes. But there were some, including an adjustment to the URL used to access a FileMaker solution.
For people that have bookmarked the FileMaker 15 WebDirect URL to your database, this presents a problem. Let’s see how we can fix it…
In this article, the most recent in our FileMaker Server (FMS) on Amazon Web Services (AWS) series, we're looking at backups. It is beyond crucial to have a good backup strategy in place, and FileMaker Server has a great backup system built into it. What we're concerned with here, though, is what we might consider to be "offsite" backups.
Let’s dig in…
Continuing our series of FileMaker Server (FMS) on Amazon Web Services (AWS), this installment looks at Elastic IPs, what they are and why you might want one. If you're not familiar with AWS and setting up FMS on an Instance, check out our other blog posts FileMaker Server on Amazon Web Services: Part 1 and FileMaker Server on Amazon Web Services: Part 2 before delving into this one.
So, let’s check out Elastic IPs…
In previous posts, we detailed a technique to capture the coordinates from a Google map and place these into a record in FileMaker. This is certainly a great way to have your users interact with maps, as long as they are using the FileMaker Pro client. If the solution deploys FileMaker WebDirect, the technique does not work. But we have a way that does and after a number of enquiries about how we did it, we’re finally getting around to documenting this and sharing with others...
Back in May of this year, Microsoft announced that it was beginning a transition of its Outlook.com email product to an Office 365 back end infrastructure. This has been ongoing and we recently encountered an issue where the credentials for a custom domain email account were being rejected, despite being correct. Here's how we fixed it.
Following up from our previous post, a reader asked if it was possible to have the marker show automatically when the map loads, if there were coordinates previously selected. Depending how Google Maps is being used in a solution, this is a perfectly reasonable expectation of functionality. So, we decided to add this to the file and post an update. There was, however, one annoying little issue...
Google has a variety of APIs for its Maps, allowing developers to access, integrate and query map data. Some time back, a client needed the ability to click on a map and capture the selected coordinates into their database, so we started our map quest using the Google Maps Javascript API v3. Since then we've had a number of enquiries as to how this was accomplished and, as a result, we've put together a demo file.
Sounds Essential LLC
PO Box 2229
Cashiers, NC 28717
t. 828-743-8350
e. info@soundsessential.com
We occasionally send out news of general interest in our fields of specialty. Sign up to stay up to date.
© 2022 Sounds Essential LLC. All rights reserved.
