The difference in time between the same script running on the client and the server is noticeable. Server simply does the work, then updates the client cache with any changed data. There’s no transfer of data back and forth. FileMaker Perform Script on Server does the complex tasks right there on the server, where the records are actually sitting. As of FileMaker 15, records are cached in the local machine, but FileMaker still might have to fetch new records, process them in some way, and then send the updated records back to the server. The AdvantageĬomplex tasks take up a lot of computing power and time when run against hosted data on a client machine. It is not supported in Runtimes, and it doesn’t make sense in Server schedules–scheduled scripts already perform on the server.Īlong with the script name and the parameter, you can specify to “Wait for Completion”. Perform Script on Server (P.S.O.S., as FileMaker devs like to call it) works in FileMaker Pro, FileMaker Go, and WebDirect. We’ll look at why this was such a game changer below. You can specify a script in the current file or external data source file, run it up on the server, and get back the result. Of course this only applies if a file is actually hosted. Its purpose is to, as it is called, perform a script on the server. This small-seeming script step was introduced in FileMaker 13. As we study it and use it properly, we’ll use this script step like a boss. Let’s discuss this script step, its features and things to watch out for. Well one method we have at our fingertips is FileMaker Perform Script on Server. We all want our custom apps to be faster, right? As problem solvers, we design our system and complex processes to happen quickly so that the user can get on with her task.
0 kommentar(er)
