>>>Grady, you're right that cursors/tables in VFP have max 254 fields if you use nulls. However, I can assure you that you can create, index and relate multiple cursors to mimic truly vast arrays. You can have thousands of such cursors at once and you can even relate between different "arrays" of cursors if you need to. Or you can use a smaller number of cursors with an extra column field so you can access multiple columns using self-joins. Either way it can be useful to "browse" your data to get a feel for it and watch for obvious SNAFUs.
>>>
>>>Alternatively you could investigate a 3rd-party dbf tool that allows thousands of columns, such as the one used by etecnologia for dbf management in their NET compiler.
>>
>>Thank you. If you've done it then I shall switch over to using cursors too. Things should be a bit speedier that way.
>
>Hey Grady
>
>I did mention such a thing to you before. You could also build a single table with a structure like x,y,content. 1.2 billion records could yield an "array" of 34,641 x 34,641

Yes you did mention it, but I thought I needed to have more than 254 fields after 254 records were available to process.