Perhaps you could have two views: a Male view and corresponding
entry/edit form
and a Female view which its corresponding entry/edit form. After the gender
question is
asked, one of two appropriate forms could appear. This form could be a copy of
the
original form but with the inapplicable fields set so data could not be entered,
or
a new form could appear which had only the applicable fields.
Another way to do this if you have 'clumps' of data which are relevant
in limited situations would be to use MDI forms. You could enter the gender
field and get a popup list showing female, male. Based on the selection,
[fvChoice] you could
ENTER/EDIT FemaleForm [.fvChoice]MDI AT 375,290,740,520 or
ENTER/EDIT MaleForm [.fvChoice] MDI AT 375,290,740,520
Since you will be editing and storing the data in an existing row, the
data goes right
where it is supposed to go without any additional convolutions.
A return from your MDI form will take you back to the form from which it
was called.
Randy Peterson
"J. Stephen Wills" wrote:
> Given this background, the EEP's are being developed to accomplish the
> several functions, with the EEP shown below handling the task of processing
> "SKIPs". IOW, some (subsequent) records may be skipped, if the input is
> determined to trigger a skip (these are pre-defined, f/ex: if the input were
> "MALE", or a code therefor, the rows/recs with inputs f/"FEMALES" would be
> skipped).
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/
