Learning Claris FileMaker

Have you experienced slow response times on your cloud-hosted FileMaker solution?

Organizations typically combat this by optimizing flows, scripts and layouts, which requires a lot of time to test, refactor and redesign.

A faster way to combat this issue is to create layouts designed for users with slow internet connections.

Here is a quick and easy method to detect high-latency users in FileMaker without using a plugin.

...

We’ve been working with a client recently who wants to host the FileMaker solution we’ve built for them on FileMaker Server – Hooray! 

We couldn’t agree more.

Using FileMaker Server (FMS) provides more flexibility, security, functionality, backups, better performance – the list goes on, but it’s a wise decision on their part.

But then comes the question, how and where to host?

There are a few options:

• Purchase FMS and a dedicated computer (Mac or PC) to run it on and host locally
• Utilize one of the many FileMaker hosting providers in the marketplace
• Set up your own FMS using one of the many cloud services available

Each of these options has their pros and cons, but they’re all viable solutions, depending on the needs of the users/organization.

The most complicated of the three is the last, as it involves a decent amount of set up, and choosing a provider from the vast market of cloud services can be daunting.

Read how you can do it with the help of 'Soundsessential'

The second part of our FileMaker Server (FMS) on Amazon Web Services (AWS) series focuses on launching our server Instance and getting FMS installed and up and running.

In our previous blog post, we did all that was necessary on the AWS side to set up groups, users and security prior to being able to launch our server Instance using AWS’ Free Tier option – a free cloud server as long as we stick within the Free Tier guidelines.

So, now that we have all that taken care of, without further ado, let’s launch and connect to our server in the sky…