FileMaker Magazine Posted February 18, 2014 Posted February 18, 2014 "}' class="video-js vjs-default-skin" width="640" height="360" controls="controls" preload="auto"> FileMakerDeployment_Full.mp4 By Matt Petrowsky Simply creating a single FileMaker file to store your data is a perfectly fine way to start your solution. However, the first few times any number of users start complaining about the workflow taking too long, is when you may need to evaluate your architecture. For sure, FileMaker Pro is a very capable platform. Like any thing else in the world of tech, there are less efficient implementations and highly optimized solutions. A knowledgable developer will known how to squeeze every bit of performance out of the environment they've chosen to develop within. The same holds true for FileMaker as for any other programming language. In this video, I walk though some of the most common and also some of the more exotic deployment models you can use with FileMaker. Essentially, it all boils down to this. Knowing that FileMaker does not care where the data is. If you can point to it, and FileMaker can see it, then it's up to you as to how you structure things. We're not just using computers now, we're using smartphones, tablets and who knows what else will be coming. Touch sensitive wallpaper within our homes of the future? Watch this video for a sense of how it's possible to vary the deployment of your FileMaker solutions. Tags: Deployment Separation Model FileMaker Go FileMaker Server View the full article
Recommended Posts
This topic is 3929 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now