(Also, if you’ve been putting off exploring Perform Script On Server, a.k.a. Bottom line: each of these three techniques can be fastest, depending on circumstances. Or, if you’d rather not do your own benchmarking, scroll down to see results from my tests. Well today we’re going to look at a couple alternatives to Fast Summaries, with the help of some demo files, which you can use to do your own benchmarking. There are various ways to accomplish this, including the Fast Summary technique, which regular readers of this blog may be familiar with, as it has made a number of appearances here over the years. If you do complex data analysis, then from time to time you probably need to group, summarize, and parse data into variables and/or fields.
#Filemaker server script update#
Update : see also Fast Summaries Re-revisited. Continue reading “PSOS – Run Script in File not open Locally” → Tagged Perform Script on Server, PSOS 9 Comments ExecuteSQL, Level: Intermediate, Version: FM 13 or later Fast Summaries Revisited Fortunately there is a “c” option not mentioned above which I’ll get to shortly, but first let’s demonstrate the issue. Hmmm… I think we can agree that from a security standpoint “b” is a non-starter, and the whole point of this article is to avoid “a”. …in other words, if you want PSOS to be able to access files, you need to either a) already have the files open client side, or b) throw caution to the wind, and configure the hosted files to auto-open with pre-entered credentials.
If we consult the online help entry for running scripts on server, the official word is that server-side scripts can access other FileMaker files only when… But of course there may be circumstances where you’d like to be able to access files server side that the user does not have open client side, either because the user’s credentials do not allow access to those files, or because you’d rather not have to open the files client side merely to facilitate a PSOS call. Here’s the behavior, or misconception, actually: a server side script initiated via PSOS (apparently) cannot access files on the server unless the user already has those files open locally.
Today I want to take a look at a certain Perform Script On Server (PSOS) behavior, and for those who find this behavior to be inconvenient, propose a work around. Update: See Jason Wood’s suggestion in the comments section for making this technique more secure.
0 kommentar(er)
