Rowland
Struggling to understand what you are looking for here... Could it be
that script parameters are what you need?
You'd have one script to handle all your possible tasks. The script
is attached to a single button. When the button is clicked, a script
parameter is passed to the script from the current record -- and you
can encode into the script parameter any data you like. It might
include the record id of the 'person who is to do' the task, a code
for the type of task to be performed, etc.
The script would call other scripts depending on the data carried by
the script parameter. These sub-scripts can also be handed any data
they need in the form of another script parameter or a variable.
That is, the logic is performed by the script -- as is usual in
Filemaker. The data required by the logic is passed around using
script parameters (and possibly variables).
Or am I missing the point somewhere? If so, you might need to give
more detail of what you are trying to achieve -- perhaps with actual
examples.
Steve
On 24 Sep 2008, at 22:49, Rowland & Wilma Carson wrote:
If you have a pointer field on the record, then the script can check
this value, and then call the appropriate sub-script
Forbes - thanks for your response, but I'm not sure I fully
understand it. Do you mean something like:
A field in the tasks table holds a unique value.
There is one script which picks up that number.
In the script there is something like:
if number = 1, do script "print newsletter labels"
if number = 2, do script "generate renewal forms"
if number = 3, do script "lapse members unpiad for this year"
and so on..
I can see that would work, but it seems a bit klunky.
But on reading your first paragraph, I was thinking that you would
want
a join table between members and tasks? So that you would know what
needs doing to who (so to speak)
I didn't actually say that the system is designed to server
multiple users, but that is indeed the case. Thus there is a need
to connect each task with who does it, not who it gets done to. The
scripts that do the actual work figure out who to do it to (with
appropriate finds etc). There is a table of users and the tasks
table includes a user ID field to relate each task to the correct
user.
