I tried using zippscript, and cannot get it to work.

I have a field with several radio button choices. I set one radio button and
hit a button nearby to run a script that selects a layout based on the radio
button choice. I want to use zippscript, so changing the radio button then
runs the script without another mouse click.

I treid a claculation to set a field with zippscript using the
zippScript_PerformScript choice, naming the FileName, correctly, and the
script I want to run, correctly. I get an error message saying it can't find
the table.

Any clues to what I am doing wrong? Is there a tutorial how to use this
plugin? The info that comes from the author is very sparse.

Thanks.

David Robins, MD wrote:

It appears that one of his optional elements is not really optional.

Using his demo file, I created a new trigger field and script to trigger.
Starting with the trigger calc copied directly from his working example, I
replaced the elements with my own, one by one.

Replacing the field name then the script name worked.

Replacing the ScriptParameter with "" worked.

Replacing the ScriptControl with "" crapped out. Putting "0" in there
worked.

Matt

Matt Wills wrote:

I should have provided an example. This should work for you:

YourField & zippScript_PerformScript ( Get ( FileName ) ; "ScriptName" ;
"" ; "0" )

Matt

On 7/27/05 4:53 AM, in article GAKFe.9864$ab2.9015@trndny07, "Matt Wills"
<I'm (AT) Witz (DOT) end> wrote:


So, If I have a trigger field, (ie a radio-button field), what kind of

script step do I use to put the

[ YourField & zippScript_PerformScript ( Get ( FileName ) ; "ScriptName" ;
calculation into?

How does concatenating the trigger field with the zippScript do anything?

Thanks.

David Robins, MD wrote:

Not a script step. The field has to be set up to auto-enter the calculation.

Open field definitions, select the field, and click Options.

Under the Auto-Enter tab, click "Calculated Value". Enter the calculation
in the "Specify Calculation" dialog. Click "OK".

Before you close the Options dialog, UNCHECK "Do Not Replace Existing
Value For Field" (you WANT it replaced).

(See AutoEnteredField in the zippScript demo as an example.)

The way these things (zippScript and the far more powerful
EventScript)work is to tack the trigger function onto the value of the
field and re-populate the field with the concatenated value.

If the field name is left out, the script will trigger, but the value you
selected for the field is gone. There's no harm in leaving the field name
out if you don't need to retain the value.

Which brings up the question: if you are taking up a fixed amount of space
with radio buttons AND if you don't retain the field value, why bother
with a script trigger at all? You could simply place a group of regular
buttons, each defined to do what you want, and be done with it.

Instead of radio buttons, I use a dropdown menu with a default value for
the field showing as the menu "name". Uses less space, but it does require
a couple of extra steps in the script that's triggered.

At the end of the triggered script, I set the field value back to the menu
name I want to show. Because doing this triggers the script again, there
has to be a trap at the beginning of the script to exit if the field value
equals the menu name.

Works like a charm, and I can put as many different menu selections as I
need in the space of one button. Using Custom Values in the value list
allows me to insert dividing lines if I want.

Matt

Matt Wills wrote:

I did a little more experimenting.

As stated previously, the script will trigger if you leave the field name
out of the calculation, but you will lose the selected value of the field.

That having happened, on what will the triggered script base its decisions?

You want to go to a certain layout based on which radio button is
selected. Your triggered script would probably look something like this:

If [Button = "A"]
Go To Layout [A]
Else If [Button = "B"]
Go To Layout [b] //etc., etc.
End If

If you don't include the selected field value in the calculation, then the
script has nothuing to work with in the If tests. Yes, the script will
trigger, but no, it won't do nuttin'. There are plenty of situations in
which retaining the selected value would not be all that important
(triggering any non-branching script), but in what you're describing, it is.

Here's a fly in the ointment.

I have a small demo file showing the drop-down menu technique I mentioned.
It's written using EventScript, so I made some changes to have it use
zippScript. Part of it works, part of it doesn't, and I haven't a clue
why. Except for the non-optional parameter we encountered earlier,
everything should work the same. I don't have time to fiddle with it right
now.

Since I am so firmly invested with techniques using EventScript and which
I know work as they should, I'm not going to spend much time on
zippScript. What we've encountered with makes me unwilling to trust it,
while I've never had a single problem with EventScript (also free).

Email me at fmpREMOVETHIS (AT) virtualvermont (DOT) com if you would like a copy of
the EventScript menu demo. I'll send along a copy of the plug if you need
it.

Matt

Matt Wills wrote:

Me again.

I managed to figure out what was happening with the zippScript Demo, so I
can provide the menu demo in either zippScript or EventScript format.

Matt

show what layout this particular reord is using. So, I keep the radio
buttons.

See, I have 4 layouts, where only a small part is unique to the layout
(refraction type for pediatric ophthalmology records). The 4 choices
determine which layout to display. The radio button chooses it. Currently, I
than have to hit a button to run a script to then go to that layout. The
main layout, showing me all the pertinent records, is in a [portal in
chronological order, and the 4 radio buttons are o view showing which one
had been used.

Yes, I guess I could use 4 individual buttons, but it would possibly be a it
more cumberson to light them up in the portal view.

BTW, I did get zippscript to work for me last night, but then it stopped
owrking and I can't get it going again. It isn't the plugin, because the
demo works.

I should look into EventScript. I have the plugin, just didn't know what is
did.

-David

David Robins, MD wrote:

I started with EventScript, and have had no problems at all. Where
zippScript appears to be a somewhat finicky one-trick pony, EventScript
reliably performs the simple trigger we've been talking about, and it has
some more advanced features, such as triggering on entry to a field.

You'll find that there is considerably more documentation in the
EventScript demo file.

More important, Gaston actually answers email.

Matt