>>I also use AMD series both at home and work and didn't face it on my own computers. But I don't think it could be a CPU bug (though I heard Pentium series still have floating point bug, AMD might be too). I would try manually erasing the VFP500.dll in ..\winnt\system directory and copying it afresh (SP3 or whatever the working copy uses - default installation doesn't do it correctly).
>>Cetin
>
>PROBLEM SOLVED!!! (I hope.) I actually took your advice one step further and found that MS released a Service Pack 3 for Visual Studio which includes the update to VFP. I checked my VFP version by right mouse clicking on the VFP.EXE and choosing Properties then Version and saw mine was BUILD 402 (the initial release version). The current one is BUILD 415! I downloaded it from Microsoft's web site and ran it and presto no more memory error (at least so far!)
>
>Thanks again!
Kevin,
One warning at this point. If you ever compile under SP3 and deliver don't forget to *manually (if not only happening to me)* erase and copy SP3 VFP500.dll also.
Cetin