I have seen memo corruption many times over. It's usually caused by faulty/unreliable hardware/network.

>This is a first. When trying to log into an application the user received the 'Invalid Memo' error 41 message. This table is not part of a dbc and contains only 5 records.
>
>I usually run Recover.app to fix a corrupted memo file. In this case there were no errors found. I then went into the table, which holds user records. Only 2 records had data in the memo field. I was able to look at one but when I attempted to view the 2nd record I received the invalid memo error.
>
>I have never had a invalid memo error that only affected a single record. I was able to fix the file using a backup but I am stumped by this behavior. Is there a limit to the number of lines in a memo field. The offending record had around 120k lines and over 2 million characters. This is a log table for a 3rd party accounting package.
>