--- Kevin Toppenberg <[EMAIL PROTECTED]> wrote:
> > Traditional Cross-References:
> >
> > AD REGULAR WHOLE FILE (#19)
> > Field: ITEM (19.01,.01)
> > 1)= S ^DIC(19,"AD",$E(X,1,30),DA(1),DA)=""
> > 2)= K ^DIC(19,"AD",$E(X,1,30),DA(1),DA)
> >
> > ...
> > >D ^%G
> >
> > Device: Right margin: 80=>
> >
> > Global ^DIC(19,"AD",10 -- NOTE: translation in effect
> > ^DIC(19,"AD",10,19,1)=
> > ^DIC(19,"AD",10,515,1)=
> > ^DIC(19,"AD",10,3393,1)=
>
> OK, so this is saying that IEN 10 can be found in the following
> places:
> record 19, and in subfile IEN 1
> record 515, subfile IEN 1
> record 3393, subfile IEN 1
>
> Is this right? If so, that should work nicely.
The DA array is the Classic Fileman equivalent of the IENS. DA is
always the IEN in the file or subfile you're considering, DA(1) is the
enclosing (sub)entry and so on. So, in this case 10 is the the internal
representation of the pointer (i.e., the value being indexed), the next
entry (19, 515 or 3393) is DA(1), or the IEN of the entry in file 19
(the OPTION file). The 1 is DA, or the IEN of the subentry in 19.01. It
just happens to be 1 in each case (the first entry in the multiple).
So, in other words: yes.
===
Gregory Woodhouse <[EMAIL PROTECTED]>
"It is foolish to answer a question that
you do not understand."
--G. Polya ("How to Solve It")
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
