Right. I was just saying this is a problem that is here to stay.

I empahsized that I felt it was a minor issue.

I don't want to hurt VFP 5.0a. I am just trying to be unbiased. We are using VFP 3.0 and are going to go to VFP 5.0, so I hope 5.0 is stable.

Take care,
Joe

>Ok, but you also can find bunch of similar things within any version of any product. The context of issue was about stability of VFP5a against another version, and this example does not hurt it much, sorry.
>
>>We have a chunk of older code from FPD 2.5 that does a seek, then a COPY TO ARRAY...WHILE...
>>
>>In VFP 3.0, it is fine. I am testing things in VFP 5.0 and that line produces an error saying "Not enough memory" or something and, if you ignore, the array has been built just fine.
>>
>>This is fixed easily enough buy DIMENSIONing the array to the correct size before the COPY TO, but I consider it a problem. However minor.
>>
>>Just pointing one out that I've found...I assumed it wasn't just a weird issue with my machine...
>>
>>Joe
>>
>>>This is VFP6 problem and I wonder what "5.0's problems are here to stay".
>>>