>>A very unusual problem:
>>I had a dbf that was 1.2G in size and had a 700M cdx - in VFP as a database with some other tables. I took the table out of the database. Then I deleted some records, packed and Then I deleted the cdx (copied it somewhere....:-) ), reindex using a prg to re-build the cdx by hand.
>>
>>I ran an application and after a while, it can't even seek or browse this table - it keeps getting hosed. If I make the app into an .EXE and run that, I get a "MEMORY IS LOW SO STREAMING OUTPUT UPDATE HAS BEEN DISABLED" error.
>>
>>
>>
>>
>> I've trapped the error in an application and after 15 records of information (I'm importing data into it from various tables) it gets to the following lines:
>>SELECT mytable
>>SEEK mVAR
>>
>>at the seek, the system freezes.
>>
>>if I do a select by hand and then a BROWSE, it also freezes....
>>any ideas?
>>
>>
>
>It could be bad index. I saw some strange things for high-volume data: table looks OK, until you hit some 'mined' value. Try to issue DELETE TAG ALL and then rebuild all tags from scratch. I got real help from this couple times.
Another thing to consider is that you may have some invalid/corrupt data in your table. I would suggest checking your table's integrity, by using something like dSalvage. (By the way does anyone know if dSalvage supports VFP tables?)