Hi Rex,

What you're describing sounds like a "regular" memo field corruption that ususally's caused by improper application shutdown or faulty hardware. Why do you think that 'Copy and Paste' is the source of the problem?


>
>I managed to get a copy of one of the users memos and I was surprised at the mess it was in. There appears to be memos from several different records amalgamated together. They are separated by a series of small squares which which I presume are 'unprintable' characters for VFP but which turn out to be a series of ASC(00) in my hex editor.
>
>Also, there are a lot of memos in the table with a capital 'M' in the memo field indicating memos present, however when the memo is opened, it is empty. There are no VFP error messages coming up, yet. Whilst trying to browse some of the memos, I eventually come up with a 'Not Responding' message and I need to give VFP the 3 finger salute to close it down and start again.
>
>I have screen print copies of one of the 'dodgy' memos and the hex print of it showing the invalid characters. I can send these to you if you like, or you can have a copy of the files (dbf and fpt) if you prefer. They are in a WinZip archive of about 855k.
>