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".
>>
>>>Hiya Ed ---
>>>
>>>The infamous C0000005 exception error :-)
>>>
>>>
>>>>What problems? I'm aware of MTS future considerations but it's obviously not applicable to mainstay development, so far :).
>>>>
>>>>>Although 6.0 has some glaring problems, I suspect I'd lean towards Garrett's opinion that they'll be soon fixed and 5.0's problems are here to stay.
>>>>>
>>>>>>I would like opinions as to which is stabler VFP 5.0 or VFP 6.0. I am new to VFP (but have trained in 6.0). The company I work for currently has an application that was developed and released in 3.0 and we are looking to upgrade it to either 5.0 or 6.0.
>>>>>>
>>>>>>Thank you.