Hi Mario,

>For some reason the memos are corrupted and there are duplicate pointers and the data is currupted, does any body know how to fix it with out loosing data, or what is the best way to approach this memo problem.

This is a known issue in FoxPro 2.5 when the codepage in the DBF header - CPDBF() - does not match the current codepage - CPCURRENT(). In this case, FoxPro duplicates everything beyond the 512th byte up to the size of the original string. If that's your problem, either set the codepage to 0 for all tables (CPZERO.PRG), make sure they match and refuse to update a memo if they don't or upgrade to FoxPro 2.6.

Besides FoxPro is known to have a lot of troubles with certain Novell clients (or vice versa). Try to search for FoxPro in the Novell KnowledgeBase.

Finally, in our application we usually close the table after updating a memo field and reopen the table afterwards. This makes it a bit slower, but so far, it has increased stability.

Christof