@AF Clarification Needed...

[Stanley - stanlyn-com]

Hi Ken,

>> (In other words, if you left the third I2, than a reference to I1 means
the third I1, and I3 means the third I3, and so on.
This helped solve my problem.

I could not use the array to a group feature as I saw you say it was new in
5.6 and I'm using 5.0.14d4

Thanks for explaining it better...

Stanley





-----Original Message-----
From: Kenneth Brody [mailto:kenbrody at spamcop.net] 
Sent: Wednesday, October 05, 2011 11:57 AM
To: Stanley - stanlyn-com
Cc: filepro-list at lists.celestial.com
Subject: Re: @AF Clarification Needed...

On 10/5/2011 11:12 AM, Stanley - stanlyn-com wrote:
> Ken,
>
>>> Alias the array to the group itself:
>>>   dim ItemNum(5):I2
> No, not to the group, instead to the first field in a contiguous block of
> fields as in
> dim ItemNum(5):38

That's fine, if the fields are contiguous.  Aliasing to the group itself 
means that it doesn't matter if they're contiguous or not.

> I will try the array to the group.
>
> To be clear, when you say "group", you mean the "A2)" and "B2)" entries
and
> not the blocks of fields that is used for the non-contiguous definitions.

Correct, just as in my example:

     dim ItemNum(5):I2

> Also, in using "A2)", to filepro, what does the "A" represent as well as
the
> number and paren?

Letter-number-paren at the start of a field name specifies it as part of an 
associated field group.  All groups with the same letter are related, so 
that, for example, in @WLFI2 you can refer to any other I* field, and it 
will mean the same instance as the I2 you just left.  (In other words, if 
you left the third I2, than a reference to I1 means the third I1, and I3 
means the third I3, and so on.  However, a reference to another letter 
group, such as A2, you will get the first instance, regardless of whether 
they are defined contiguously or not.)

[...]

-- 
Kenneth Brody