Peter,

I have NOT read the whole thread...

IF you are doing a COPY TO ARRAY then a bug in VFP can cuase this error message *if* the array named in the COPY TO is not pre-dimensioned.
The solution in this case is simply to dimension it (any size) first.

good luck


>Thomas,
>
>I agree, most times the obvious solution is the right one.
>I was not aware of the fact that VFP had those kind of problems, but I've always found that it, at least in the area of control over memory handling, left a lot to be desired.
>
>On the practical side of this problem: theres no way in hell, that my client's going to let me muck around with downsizing his machines, physically or otherwise.
>
>Thank's for the suggestion,though.
>
>BR
>
>Peter
>
>
>
>>Peter,
>>>3) Yh Yau: Remove memory? I do have more than 256MB, should I really physically downsize? This is VFP 8.0, we're in the 21st century, are you serious?
>>VFP makes some assumptions about the hardware depending on OS, physical memory, swappable memory and so on.
>>
>>Sometimes it is easier to bulldoze through with less memory before trying to analyze all the possible side effects.
>>
>>You don't need to physically remove the RAM, the /maxmem in the boot.ini should be enough.
>>
>>
>>HTH
>>
>>thomas