>Hi Keith,
>
>I had this very same problem. We would have 200-300 memo's dissapear in one day, work fine for another month or two and then again another 200-300 would disappear.
>
>We had to do the following to fix the problem. Create a new table, append from the original and then recreate the CDX. This seemed to have solved the problem. At least we have not had a reoccurance in several months.
>

Ken --

That was a fix that we typically used too. Apparently the APPEND FROM reconciles the memo pointers in the DBF with the locations in the FPT in the process. I heard that there was a utility on the market several years ago for repairing memos, and that's all it did!

Glad to see you're back in Traverse City after DevCon. Didn't have a chance to say goodbye. I joined a group of Indy consultants who rented a van. We drove back straight thru -- 34 hours. Had the worst jet lag I've ever had -- and I didn't even fly!

Hope your trip was relatively uneventful <g>.

Jay


>
>
>
>>I would appreciate any ideas regarding the following mysterious problem:
>>
>>I have inherited a VFP application that interacts with a FOX DOS application. It saves its data by stuffing it in the memo fields of the FOX DOS tables. It stores multiple 'fields' in one memo by using XML-like tags.
>>
>>Intermittantly users will get the following: They save data to the DOS memo fields, then return to find it has disappeared completely. This happens about 2-3 times a month, under fairly heavy use. Sometimes the pointer of the memo field in question seems to be corrupt (i.e. pointing somewhere past the end of the .fpt file) but not always. I haven't been able to reproduce the problem or even identify any pattern to the occurances.
>>
>>Another intermittant problem: The dreaded C0000005 error comes up now and then, again without any clear pattern to it. I did take care to make sure all objects are cleaned-up properly, but this didn't seem to help.
>>
>>The user workstations are Windows 98, accessing the .exe and data over a LAN, using the Microsoft client.
>>
>>
>>Do you think that concurrent access by FOX DOS and VFP to the same table and memo could be a root cause of these problems, or should I look elsewhere?
>>
>>Thanks in advance for any ideas.