>>I'm not real sure this will help. If I were you I would set up the array in the calling program and then pass the array to the form. In the INIT of the form store the array to a local property just to check against. Then do what ever you want to the array. BTW I believe it is not required to set UFPARMS - just use the '@'.
>
>It won't, since the array is passed into the Init, and would go out-of-scope and become unavailable to subsequent methods.
>
>The best approach here IMO is to create a parameter object that holds the member array you want to pass; pass the object reference to the Form's Init. Save the passed object reference to a custom member property of the form, and then refer to the array via the saved object reference. You can change the contents and dimensioning of the object through the object reference, and on termination, the original object passed in would hold the modified array - in fact, at all times, the origianl object and the member property copy of the object reference point to the same thing.

Thanks! I had begun to relegate myself to the parameter object but wanted to make sure that I wasn't missing something obvious as is often the case.

Matt