Comments on: FileMaker – Passing Multiple Script Parameters

By: Geoff Coffey

Geoff Coffey — Tue, 18 Nov 2008 16:16:33 +0000

Kirk:

No harm done to the pooch, so far as I can tell. Jesse’s solution is just a more generalized approach that can be used:

1: For as many parameters as you want
2: Reliably with any data
3: Consistently across many different scripts with no specialized knowledge

The idea is that you can use custom functions to easily handle the “tricky” part of passing parameters, so that when you actually pass and receive them, it is simple.

Geoff

By: Kirk Rheinlander

Kirk Rheinlander — Mon, 17 Nov 2008 17:55:19 +0000

I ran into a need for this function recently, converting a FM9 solution to IWP deployment, and the requirement for the non-supported custom dialog boxes, of which I had used 42 in the FM application. 35 of which, however, were pure informational on failure to complete something (OK is the only response, met with a resume script step to handle the modal response), but were of 2 different sizes; one with 20+- words, and the other with 200+- words. In IWP, this doesn’t matter – it’ll use the entire browser window. However, some clients will be using the FMremote, and, rather than leave the custom dialog function, and trapping the web access user in a conditional statement, I put a S_ or L_ in front of the script parameter. Parsing for the first character, gives me the conditional for Small or Large window size, while the remainder of the now field-level-metadata script parameter provides the conditional to pick up the right text to display in a single global field. The underscore is not as pretty as the paragraph delimiter, but is easy to read, and displays on a single line.

Not having any problems, but have I “screwed-the-pooch” someplace in this approach??

By: Jesse Antunes

Jesse Antunes — Sun, 09 Sep 2007 15:26:07 +0000

@Charles – That is exactly how we do it in our fp7 solutions…. To tell you the truth I have no idea why I wrote it the way I did for this article. Thanks for the tip.

By: Charles Houghton-Webb

Charles Houghton-Webb — Sun, 09 Sep 2007 12:02:07 +0000

A solution I’ve been using since FP7 is more or less your code, but as a simple “one liner”

Substitute ( MiddleValues ( Get( ScriptParameter );n;1) ; Â¶ ; “” )

where n is the parameter you want to get.

The parameters are sent the same way :
Parameter1 & Â¶ & Parameter2 & Â¶ & Parameter3 … etc.

It’s perhaps just a little tidier than your way

By: Geoff Coffey

Geoff Coffey — Thu, 12 Jul 2007 16:39:28 +0000

@david: You are absolutely right. The only trouble is GetValue doesn’t exist in FileMaker 7, and for reasons client-inspired, this technique needed 7 support. Maybe someday we’ll update the calcs to be a little cleaner in 8+. Thanks for the input

PS: Jesse will be posting his even cooler advanced multi-parameter system shortly. This is the one we use in every project now. It makes complex scripting so much more fun…

Geoff

By: David Richards

David Richards — Thu, 12 Jul 2007 16:23:59 +0000

Use the ‘GetValue’ function instead of ‘MiddleValues’, you won’t need to remove the carriage returns.