>From one newbie to another, I don't see any reason to have many ElseIf
branches from the root of the taf. Each one can have an _function=
add_this, _function = add_that
then call each action from a form or button with a link to
<@appfile>?_function=add_this
Hope this helps
Regards,
Len Wright
Plus International Corp
www.plusinternational.com
Direct: 604-415-2384
Fax:604-415-0830
>>> [EMAIL PROTECTED] 05/25/02 06:52PM >>>
I have a really basic methodology question: whether or how to insert
builder actions inside if actions. Take the following taf,
if menu
elseif add this
elseif add that
elseif search
I'd like to insert a new record builder into if actions add this, add
that, and search, but of course, the browser can't find the embedded if
arguments created by the builder. So here's the question:
should I make a new taf for each of the else if actions I want a
builder
for, or drag the builder if actions out to the same level as the main
if actions, thereby have a ton of if and else if actions. I couldn't
find a way to embed builder actions.
Of course, I am also exhibiting newbieness about different basic
approaches to creating a simple application.
Thanks in advance for the anticipated list sagacity!
John
by the way, I will be starting a new job in June, as director of
Technology for Lakeside School, which some of you may recognize as the
ground zero of microsoft. I plan on introducing the school to the joys
of Witango.
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to
[EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
