I'm not sure I fully understand the situation, but it does seem like you'd be better off using cursors than arrays. You can create a temporary cursor as easy as an array and the structure is just as flexible. See CREATE CURSOR in the VFP help.

>I'm building a process that stores data in arrays prior to being inserted into a series of SQL database tables. I chose arrays because I don't know the structure of the destination table until the process begins. Arrays give me the flexibility to work with any and differing structures. The arrays work fine with one "minor" problem: the 65K element limit is sometimes exceeded. I'm looking for a way to monitor the collective sizes of my arrays ( there are lots more than one in this process and it appears that all of them contribute to the 65K element limit ) so that I can dump the data out of the arrays before I run into the limit.
>BTW, I used arrays instead of remote views because I can make arrays properties of an object. This simplified keeping track of the process.