If that's the problem, why not just use MyArray[1] instead?

-Michelle


>Hi Mark,
>
>Here's the problem:
>The array expression:
>MyArray(1)
>
>looks exactly like the function call:
>MyArray(1)
>
>VFP thinks this is supposed to be a function. Fox will not determine that it is an array because you DIMENSION'ed in earlier in the code. If it could, there would be no reason for the EXTERNAL ARRAY directive that is needed in PRG's.
>
>One way around, is to use EVAL() in the report expression:
>
>EVAL("MyArray(1)")
>
>Mark
>
>>Here is my problem, hopefully it's clearly defined:
>>
>>I've created a project that contains a report.
>>That report directly references arrays.
>>
>>Every time I build the project into an EXE I get error messages informing me that the arrays are undefined.
>>
>>Is there any way to reference arrays in a report contained in a project and be able to build an EXE without getting those annoying errors?!?!
>>
>>I don't think its "unusual" to use arrays in reports -- I really find it hard to believe that the project manager will ALWAYS report array references as errors - but that seems to be the case!
>>
>>Anyone know how to get around this??
>>
>>--Mark