Another way is to include the following in the procedure that uses the array:

external array My_Array

However, there are certain areas (e.g. reports) where this technique doesn't work and your solution takes care of those.

>Wow, I found the answer. You make a PROCEDURE which you do not call, where you make the array PUBLIC. This stops the message.
>Example:
> PROCEDURE nocall
> PUBLIC my_array
>
>
>
>
>>Okay, now that I've spent many hours trying to track down any suggestion to resolve this problem, and I've tried everything I can think of (such as #DEFINE and so on), I have to ask the UT community:
>>
>> When I have an array reference in a report form
>> ( for example, my_array[1,2] )
>> then, after the build I get an "error" listed in the error log:
>>
>> ---> Report my_repo.frx has the following errors:
>> ---> Unknown MY_ARRAY - Undefined
>>
>> Is there a way to avoid this "undefined" message during a build?