<quote who='Brutzman, Bill' date='Thursday 02 August 2007'>
> What are the advantages of defining in the data dictionary mv associations?
>
> Does it mean that if I change or insert via a UniBasic writev command, that
> all of the associated fields get a null character if the program does not
> explictly specify a change?
>
> Are there any downsides to just defining a vanilla "M" field that is used
> with other associated M fields.
It's surely easier to display when listing data because you just list the
association name, not each of the fields.
Likewise, for using WHEN ASSOCIATED, fields must be associated or it won't
work.
Here's a real example with associated listed of Question/Answer IDs in a
student record: XHSTU.QA is an association of XHSTU.QUESTIONS and
XHSTU.ANSWERS
LIST H08.STUDENTS XHSTU.QA
which is automatically expanded to the read field names:
LIST H08.STUDENTS XHSTU.QUESTIONS XHSTU.ANSWERS
H08.STUDENTS.................... Questions Answers
1410792 Q116 A02
Q117 A01
Q115 A02
Q104 A150
Q97 A151
Q93 A150
Q95 A150
Q90 A150
Q111 A151
This the only reason to use associations, but one.
Jeff Butera, Ph.D.
Administrative Systems
Hampshire College
[EMAIL PROTECTED]
413-559-5556
"Daddy - did you lose your mind?"
Catherine Butera
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
