![]() We used Amazon Web Services (AWS) to launch a dedicated server for each client and then migrated them to FileMaker 15 using configuration best practices. Instead, we started setting up servers and hosting environments for clients on a per-project basis. ![]() We value our clients as partners, and every option felt like we could be steering them in the wrong direction. We didn’t feel comfortable recommending any of them. None of them are very attractive, now are they? While a good short-term solution, this is not the most sustainable option, obviously. An on-site server presents a huge array of potential issues for a company unfamiliar with server setup, maintenance, and security. This is a scarier version of the option above. Purchase FileMaker Cloud. Thile this add-on service from FileMaker itself does eliminate many headaches associated with hosting, it still requires technical expertise for a flawless setup, configuration, and end-to-end implementation.FileMaker users are on their own for migration, configuration, and maintenance. Amazon Web Services offers inexpensive servers and hosting space but offer little support. These companies are either overly expensive for little support or are incredibly cheap but offer no support at all. We reacted to the news by helping our clients navigate the options available to them. ![]() And that’s something most FileMaker users don’t have.Īlmost immediately, FileMaker users started scrambling for answers and a recommendation on what to do next. FileMaker 15 requires each customer to have his or her own server. ![]() We love helping clients learn about new capabilities and leverage the new opportunities to strengthen their solutions.īut I’ll be honest, the last release threw us – and our clients – for a bit of a loop. Our team is always pretty pumped about the new features of a FileMaker release. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |