I have seen this sort of behaviour years ago with FoxPro 2.6, in situations where the memo pointers had got messed up, almost certainly due to crashing. I had a little PRG that would just scan the memo file and clear the memo fields for any record where MLINES() came back with a ridiculous number. Never seen in in VFP though.
-- Alan Bourke alanpbourke (at) fastmail (dot) fm _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/1411983399.1179012.172872701.72ad3...@webmail.messagingengine.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
