For what it's word, an "object" that stood in for an array or a collection could accomplish the array functions that are missing; eg.

1) a property used to track the number of elements (if it's zero, the array is empty) and another to represent the actual array.

2) passing "{1,2,3,4}", etc, to the .Init() event could handle array initialization (after parsing of course).

3) custom methods to simulate AADD(), etc. would increment/decrement the property in (1) above, including the sizing of the array.

It's worth noting that we rarely get a feature added to VFP if it can be programmed in VFP itself.

The above is more in line with the way new "classes" are implemented these days; eg. the CString class in VC++.