Two ways to resolve this. I prefer the second method as I've found the first unreliable

1) EXTERNAL taTest

2) Create a procedure in your Main.prg as follows

PROCEDURE Dummy
PUBLIC taTest

Because you never call Dummy, the array is never made public. It just gets the compiler to shutup.

>In my never-ending quest for TFS 2010 glory, I've been experimenting with automating our builds. The issue I've run into is something related to what happens when we currently build.
>
>We get errors about unknown or undefined items, to which we click Ignore All and the build succeeds and the executable runs just fine. Rather than go down the road of trying to figure out how the automation process can ignore these build errors, I was wondering if someone could give me a tip on how to resolve these items.
>
>For example, one of the compilation issues regards an array that's showing up as undefined. This array is declared as a parameter (e.g., LPARAMETERS taTest) and is passed in by reference. Does the array parameter need to be more strictly defined like LPARAMETERS taTest(1)?