@AF Clarification Needed...

Tue Oct 4 20:00:21 PDT 2011

Ken, here is the table layout that contains both @af contiguous groups (all
"*1)" from field 1 thru field 89 that works ok.  The non-contiguous "*2)"
groups start at field 90 thru the end, and does not work.

1- Invoice Number, (last  19- B1) BankAcct #4      37- *
2- Notes                  20- B1) BankAcct #5      38- D1) PayDate #1
3- Invoice Date           21- B1) BankAcct #6      39- D1) PayDate #2
4- Terms                  22- B1) BankAcct #7      40- D1) PayDate #3
5- Due Date               23- B1) BankAcct #8      41- D1) PayDate #4
6- Invoice Total          24- B1) BankAcct #9      42- D1) PayDate #5
7- Vendor #               25- B1) BankAcct #10     43- D1) PayDate #6
8- HOLD, Don't Pay?  Y/N  26- *                    44- D1) PayDate #7
9- Vendor #, by Date      27- C1) Payment #1       45- D1) PayDate #8
10- On-HOLD Reason        28- C1) Payment #2       46- D1) PayDate #9
11- Company Name          29- C1) Payment #3       47- D1) PayDate #10
12- Invoice Balance       30- C1) Payment #4       48- *
13- Inv Number, (first 8  31- C1) Payment #5       49- G1) G/L Code #1
14- Last Update_Date      32- C1) Payment #6       50- G1) G/L Code #2
15- Last Update_User      33- C1) Payment #7       51- G1) G/L Code #3
16- B1) BankAcct #1       34- C1) Payment #8       52- G1) G/L Code #4
17- B1) BankAcct #2       35- C1) Payment #9       53- G1) G/L Code #5
18- B1) BamkAcct #3       36- C1) Payment #10      54- G1) G/L Code #6

55- G1) G/L Code #7             73- F1) Payment #3 Accoun
56- G1) G/L Code #8             74- F1) Payment #4 Accoun
57- G1) G/L Code #9             75- F1) Payment #5 Accoun
58- G1) G/L Code #10            76- F1) Payment #6 Accoun
59- *                           77- F1) Payment #7 Accoun
60- T1) PayAmount #1            78- F1) Payment #8 Accoun
61- T1) PayAmount #2            79- F1) Payment #9 Accoun
62- T1) PayAmount #3            80- F1) Payment #10 Accou
63- T1) PayAmount #4            81- *
64- T1) PayAmount #5            82- Audited By
65- T1) PayAmount #6            83- Created By
66- T1) PayAmount #7            84- Date Created
67- T1) PayAmount #8            85- Invoice Time
68- T1) PayAmount #9            86- Received By
69- T1) PayAmount #10           87- Location
70- *                           88- *
71- F1) Payment #1 Accoun       89- Key
72- F1) Payment #2 Accoun       90- I2) Item #1

91- Q2) Qty #1             109- D2) Desc #3
92- M2) UOM #1             110- G2) GL #3
93- D2) Desc #1            111- T2) Total Cost #3
94- G2) GL #1              112- *
95- T2) Total Cost #1      113- *
96- *                      114- I2) Item #4
97- *                      115- Q2) Qty #4
98- I2) Item #2            116- M2) UOM #4
99- Q2) Qty #1             117- D2) Desc #4
100- M2) UOM #2            118- G2) GL #4
101- D2) Desc #2           119- T2) Total Cost #4
102- G2) GL #2             120- *
103- T2) Total Cost #2     121- *
104- *                     122- I2) Item #5
105- *                     123- Q2) Qty #5
106- I2) Item #3           124- M2) UOM #5
107- Q2) Qty #3            125- D2) Desc #5
108- M2) UOM #3            126- G2) GL #5

127- T2) Total Cost #5     145- *
128- *                     146- I2) Item #8
129- *                     147- Q2) Qty #8
130- I2) Item #6           148- M2) UOM #8
131- Q2) Qty #6            149- D2) Desc #8
132- M2) UOM #6            150- G2) GL #8
133- D2) Desc #6           151- T2) Total Cost #8
134- G2) GL #6             152- *
135- T2) Total Cost #6     153- *
136- *                     154- I2) Item #9
137- *                     155- Q2) Qty #9
138- I2) Item #7           156- M2) UOM #9
139- Q2) Qty #7            157- D2) Desc #9
140- M2) UOM #7            158- G2) GL #9
141- D2) Desc #7           159- T2) Total Cost #9
142- G2) GL #7             160- *
143- T2) Total Cost #7     
144- *                     

Stanley

-----Original Message-----
From: Kenneth Brody [mailto:kenbrody at spamcop.net] 
Sent: Tuesday, October 04, 2011 1:17 PM
To: Stanley - stanlyn-com
Cc: filepro-list at lists.celestial.com
Subject: Re: @AF Clarification Needed...

On 10/4/2011 12:39 PM, Stanley - stanlyn-com wrote:
>>> Can you define "having problems with @AF"?
> Yes Ken,
[...]
> @wlfI2)
> If  : I2) eq ".sh"
> Then: G2)="6055-475" ; I2)="SHIPPING" ; D2)="Shipping"
>
> The debugger is reporting I2)=.sh as it should, @af is eq to 5 as it
should,
> now the problem... D2), Q2), M2) are all showing their values from the 1st
> set as if @af=1, and will proceed to overwrite them.
>
> I have never experienced this when the associated fields are contiguous.
[...]

What you are experiencing has nothing to do with whether the fields are 
contiguous in the file definition.  And, given the same fields, but set 
contiguously in the definition, you will see the exact same behavior.

The problem you are experiencing is due to the fact that you have given the 
fields different group letters, making the separate and distinct.  Within 
the event for one of the I* groups, only references to fields in the I* 
group will be affected by @AF.

I guarantee that if you look at the files where this is "working" that you 
will see that all of the fields are in the same group.  (ie: "I1)", "I2)", 
and "I3)", rather than "I2)", "D2)", and "Q2)".)

-- 
Kenneth Brody