This may not be the anwer your looking for but......

I had a similar problem recently and decided to get rid of the offending memo field in my table my creating a mock memo field. I allowed the user to edit a memo-like field but instead of storing the contents within an actual memo field I parsed the "memo" entry into 100 character records in a "Memo" table. When the user wanted to view the memo I simply reconstructed it from the parsed records and voila'. It acts like a memo field, but does not corrupt as easily as a true memo field does. This was a great solution for my problem, perhaps it could help you. There's a bit of coding involved but I haven't spent a single minute on blown memo's since.