Bookmarks

Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries

078274121, info0a ip, should prodicers of software_based services be held liable or not liable for economic injuries, should producers of soft ware based services such as ATMs be held liable for economic injuries suffered when their systems fail?, nisc wwwxxx, wwwxxx0cm, should producers of software-based services, such as atms, be held liable for economic injuries suffered when their systems fail?, wwwxxx0cm, www.webdp.net, Event 9 IIS log failed to write entry

Links

XODOX
Impressum

#1: block use of a series of editfields

Posted on 2008-04-15 02:53:04 by Railman

I had no idea how to word the Subject Line. What I want to do is block
access to a series of edit fields if a particular answer is given. For
Example: If the gender is asked m/f and the person enters m then all
the female edit fields would be blocked [of course the opposite].

Mac OS 10.4 FM 8.0v1
--
A second cup of coffee always works for me

Report this message

#2: Re: block use of a series of editfields

Posted on 2008-04-15 13:10:56 by E W P Appeldoorn

"Ron Lambert" <railman@sasktel.net> schreef in bericht
news:2008041418530416807-railman@sasktelnet...
>I had no idea how to word the Subject Line. What I want to do is block
>access to a series of edit fields if a particular answer is given. For
>Example: If the gender is asked m/f and the person enters m then all the
>female edit fields would be blocked [of course the opposite].
>
> Mac OS 10.4 FM 8.0v1
> --
> A second cup of coffee always works for me
>

One way could be to use portals, but when you create more choises you have
to create more portals. Why not present just the questions you need on one
layout then branching to a next depending on the choises that were made?

Portal solution: I go with the M/F choise

field gender <text ; M / F >
field cMale < Calculation ; text ; gender = "M" >
field cFemale < Calculation ; text; gender = "F" >
field cConstant < Calculation; number; 1 >

relation cMale::cConstant
relation c Female::cConstant

on your layout create the portals for both relations.
In the portal for male you put the fields that need to be visible when the
user has entered M
In the portal for female you put the fields that need to be visible when the
user has entered F

As long as nothing is entered fields remain invisible, but as soon as the
user commits the record (by tabbing out of the field) the calcs will do
their stuff.

Keep well, Urus

Report this message