>>>>My company purchased a VFP 5 software package. I have been tasked with trying to figure out why it runs so slowly. When I built the application it generated about 40 undefined errors due to array references//parameters. I know these errors don't hurt the execution but I like things clean. I decided to get rid of them by adding EXTERNAL ARRAY declarations where needed. I did this to the PRG and SCX files and got the number of errors down to 7.
>>>>
>>>>Now I'm trying to get rid of these errors in reports where the field control sources are array elements (don't know why they didn't just create a cursor). Where can I put the EXTERNAL ARRAY declaration in reports to get rid of the errors. I tried putting it in the On Entry expression for the report band, but that didn't do it.
>>>>
>>>>Thanks in advance,
>>>
>>>You can declare the array in the calling module or form. That will make it visible throughout the report.
>>
>>Thanks Evan,
>>Now all I have have to do is find the calling module. That will be fun. It is a monster application that creates a 21 MB EXE.
>
>My god! I thought I was doing bad with a 3mb EXE. :-)

Evan,
I too thought my applications were getting big when they got up to 3MB. Then I saw this one. It takes around 20 to 30 minutes to build the EXE and I can't just go to lunch while it compiles because I have to wait until the 1st undefined error pops up so I can click the Ignore All button.