>>>>>I used to know this....
>>>>>
>>>>>I'm using array lookups (i.e. ASCAN(ARRMOB,[value of field]) in the fields of my reports; when I build the project, the arrays show up as errors:
>>>>>
>>>>> Unknown ARRMOB - undefined
>>>>>
>>>>>These array definitions are not in my procedure file, but in the .SPR that calls the reports. I know that placing an EXTERNAL ARRAY line in a procedure will get rid of this error, but how do I get rid of them in a report?
>>>>
>>>>(i think) put the EXTERNAL ARRAY in the .spr setup code
>>>
>>>I had the same problem, and I putted 'EXTERNAL ARRAY' every
>>>where and it just didn't work, I ended up ignoring the
>>>error, because anyways at run time if the array exist
>>>it will work fine.
>>
>>i know, but it is annoying. of course, i may be remembering the wrong snippet area...
>
>How does #SECTION 1 sound?

that sounds familiar -- i knew i was forgetting something. BTW, what does #SECTION 2 do? is 1 for parameters and 2 for external arrays?